Version 5.0.5 (June 2023)
- 28 Oct 2024
- 2 Minutes to read
- DarkLight
Version 5.0.5 (June 2023)
- Updated on 28 Oct 2024
- 2 Minutes to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Supported platform versions
iOS 11.0 – iOS 16
With the end of support for iOS 9.0, support for 32-bit architectures also ends.
iPadOS 16
Xcode 12 and later. We recommend using the latest stable version of Xcode, currently 14.1.
iOS platform updates
App Shielding version 5.0.5 is compatible with iOS/iPadOS 16.
As of July 1, 2022, App Shielding for iOS version 4.2.0.39844 and earlier are no longer supported. For more information, refer to the OneSpan Customer Portal at https://cp.onespan.com/.
New features and other updates
Changed naming scheme for bound package and shielded application
We have changed the naming schema of the bound package contained within a .zip file as well as the .zip file itself. The file name prefix has changed from “wrapped” to “shielded”.
Old naming schema:
wrapped-<original package file name>.<original package file extension>
wrapped-<original shielded application name>.zip
New naming schema:
shielded-<original package file name>.<original package file extension>
shielded-<original shielded application name>.zip
Fixes and other changes
SHIOS-2093: Improve "Unknown architecture in library" error in the Shielding Tool
Description: Some frameworks may have additional architectures embedded, which are irrelevant for the Shielding Tool, such as the armv7k architecture for older generations of Apple Watch.
Status: This issue has been fixed. The Shielding Tool will no longer display warnings about such libraries being present in the shielded application.
SHIOS-2255: Remove exposed Shield SDK namespace classes when not enabled
Description: Some third party code may have names which conflict with a Shield SDK namespace, for example Secure Local Storage.
Status: This issue has been fixed. The SecureLocalStorage namespace has been removed from App Shielding packages where this API is not enabled.
SHIOS-2283: Application terminates unexpectedly due to 'symbol not found'
Description: In the Shielding Tool, the load order of frameworks for the app has been rewritten to ensure App Shielding is always loaded first. In rare cases, this re-ordering may cause problems for some non-weak symbols causing the app to terminate unexpectedly when launched.
Status: This issue has been fixed.
Known limitations
The limitations described here have not yet been solved for the current Mobile Application Shielding version. Possible workarounds are described where available.
XCFramework support
App Shielding is provided both as framework and as XCFramework. If you are using a legacy build system on Xcode 11 and later, use the ShieldSDK.framework instead of the newer ShieldSDK.xcframework. Xcode will cause an error when using the XCFramework in the legacy build system.
ARM64E limited support
The ShieldSDK framework is not compiled for the ARM64E CPU architecture, and therefore does not include the corresponding slices. ARM64 CPU ABI should be used instead. At the moment, Xcode 11 does not create an ARM64E target by default. Consequently, no action is required at this point.
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?