You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently facing an issue with the jailbreak detection feature in the jail-monkey library after upgrading our React Native application to a newer version. Prior to the upgrade, the isJailBroken() method was functioning correctly and returning true as expected when running the app on both Android emulator and iOS simulator.
However, post the React Native upgrade, the isJailBroken() method now consistently returns false when the app is run on the emulator.
Additional Information:
React Native Version: 0.72.5
jail-monkey Version: 2.8.0
Emulator: Android Studio Emulator
We have thoroughly checked for changes in the React Native upgrade documentation and the jail-monkey release notes but haven't found any relevant information. Any guidance or insights into resolving this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I guess this is not relevant to react-native upgrade @iremyk . After I investigate to implementation of isJailBroken function. It is returning if the target is simulator.
We are currently facing an issue with the jailbreak detection feature in the
jail-monkey
library after upgrading our React Native application to a newer version. Prior to the upgrade, theisJailBroken()
method was functioning correctly and returning true as expected when running the app on both Android emulator and iOS simulator.However, post the React Native upgrade, the
isJailBroken()
method now consistently returns false when the app is run on the emulator.Additional Information:
We have thoroughly checked for changes in the React Native upgrade documentation and the
jail-monkey
release notes but haven't found any relevant information. Any guidance or insights into resolving this issue would be greatly appreciated.The text was updated successfully, but these errors were encountered: