Version 6.5.3 (June 2024)
- 28 Oct 2024
- 2 Minutes to read
- Print
- Dark
- PDF
Version 6.5.3 (June 2024)
- Updated on 28 Oct 2024
- 2 Minutes to read
- Print
- Dark
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Supported platform versions
iOS 12.0 – iOS/iPadOS 17
With the end of support for iOS 9.0, support for 32-bit architectures also ended.
Shielding Tool:
Windows 10: 64-bit Java 17
Mac OSX (10.15+)
The Shielding Tool requires a macOS system to sign applications.
Ubuntu Linux 20.04 LTS or 22.04
Xcode 12 and later. We recommend using the latest Xcode version.
iOS platform updates
App Shielding version 6.5.3 is compatible with iOS/iPadOS 17.5.
As of March 1, 2024, App Shielding for iOS version 4.3.8.69424 and earlier are no longer supported. For more information, refer to the OneSpan Customer Portal at https://cp.onespan.com/ or the OneSpan Mobile Portal.
Deprecations
Platform minimum supported version
The minimum supported version is iOS 12. App Shielding no longer supports iOS 11.
Xcode
As of Xcode 14, Apple has deprecated bitcode.
As of App Shielding version 6.0.0, the Shielding Tool no longer supports bitcode-based code obfuscation!
Deprecated API
As of App Shielding version 6.5.0, the ShieldCallback API has been deprecated and will be removed in a future version. This API has been replaced with the new PRMShieldEventManager and PRMShieldEventDelegate protocols that have been integrated into the ShieldSDK callback APIs.
See also the New features and other updates section of the Release Notes for version 6.5.0. For more information about the integration, see Configure callbacks on iOS.
New features and other updates
In App Shielding version 6.5.0, new callback features have been added, deprecating the old ShieldCallback API:
New callback protocols
New protocols have been integrated into the callback APIs for ShieldSDK, PRMShieldEventManager and PRMShieldEventDelegate. The old ShieldCallback API is still available but is marked as deprecated and will be removed in the future.
See also New features and other updates. For more information about the integration, see Configure callbacks on iOS.
New callback testing and development interface
ShieldSDK provides a new interface for testing and development purposes, PRMShieldCallbackTestManager. This API allows you to trigger events with the desired value (e.g., the device is jailbroken) and a delay when the event should be triggered. This API will not trigger any security checks to run, only the desired event that you want to validate. Refer to the "Triggering Callbacks" section of the documentation for more details.
Note that this code is for debugging only and should not exist in the binary when shielding it, as these calls in a shielded app will cause the app to crash. This feature will not be available after shielding, as the Shielding Tool will replace the stub library with the actual App Shielding library.
For more information, see Configure callbacks on iOS - Debugging: manual triggering of callbacks.
Fixes and other changes
SHIOS-1935: Added removeObserver API
Description: The removeObserver API was added to App Shielding. Observers added with the addObserver method of the PRMShieldEventManager API can now be removed with the removeObserver method.
SHIOS-2689: Moved App Shielding Xcode integration into post-build action
Description: The App Shielding Xcode integration can now be performed through a post-build action. This makes the integration more resilient to changes in Xcode (comparing with the current Xcode integration performed during the build phase).
SHIOS-2855: ShieldSDK.xcframework signature
Description: ShieldSDK.xcframework is now signed with a OneSpan certificate.
Known limitations
The limitations described here have not yet been solved for the current Mobile Application Shielding version. Possible workarounds are described where available.
External screen block
Blocking external screens (e.g. AirPlay) is currently not working for apps that use UISceneDelegate in iOS 13 and later.
Was this article helpful?
