Callbacks on iOS

Methods

List of callback methods
Callback Description
jailbreakStatus

Provides a boolean that indicates whether the device on which the application is running is jailbroken.

repackagingStatus

Provides a boolean that indicates whether the application has been repackaged. If the application is running in an emulator, this method is not called.

screenRecordingStatus

Provides a boolean that indicates whether one or more screens used by the app is being recorded.

developerModeStatus

Provides a boolean that indicates whether Developer Mode is enabled on the device. Developer Mode was added in iOS 16, so this method is not called on devices running iOS 15 and earlier. Such devices are considered to have Developer Mode enabled by default.

debuggerStatus

Provides a boolean that indicates whether a debugger is attached to the host application. If App Shielding is configured to block debuggers, this method is not called.

screenshotDetected

Called when App Shielding discovers that a screenshot of the application has been taken. If the application is running in an emulator this method is not called.

libraryInjectionPrevented

Called when App Shielding has prevented an untrusted library from being injected into the process during runtime.

libraryInjectionDetected

Called when App Shielding has detected that there are untrusted libraries in the process. In production, however, you should configure App Shielding to use the exitOnLibraryInjection option, and not rely on handling a callback.

hookingFrameworksDetected

Called when App Shielding has detected that there are hooking frameworks in the process. In production, however, you should configure App Shielding to use the exitOnHookingFrameworks option and not rely on handling a callback.

Exit on... security options like exitOnJailbreak will cause the application to immediately exit before the corresponding callback is triggered. Also note that some of these options, like exitOnRepackaging, are always enabled in release mode.