Version 6.0.2 (November 2023)

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.

• iPadOS 17

• Shielding Tool:

  • Windows 10: 64-bit Java 17

  • Mac OSX (10.9+)

    The Shielding Tool requires a macOS system to sign applications.

  • Ubuntu Linux 20.04 LTS or 22.04 LTS

• Xcode 12 and later. We recommend using the latest Xcode version.

iOS platform updates

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/.

Deprecations

iOS: 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!

New features and other updates

Trigger ShieldSDK callbacks for debugging/testing unshielded apps in the iOS simulator and on real devices

ShieldSDK provides a new API for the debugging purposes. The new debugging API allows you to trigger callbacks with the desired value and delay when the callback should be triggered. This API will not trigger any checks to be run but rather the desired callback which one wants to validate.

---
- (void)triggerJailbreakStatus:(BOOL)value afterDelay:(NSTimeInterval)delay;
- (void)triggerEmulatorDetectedAfterDelay:(NSTimeInterval)delay;
...
---

This code is for debugging purpose only and should not exist in the binary when shielding it. When these calls are included in a shielded app, the app will terminate unexpectedly.

This feature will not be available after shielding, as the Shielding Tool will replace the stub library with the actual App Shielding library.

Fixes and other changes

Deprecated features

ShieldSDK.framework

Fixes

RASP-3405: Incorrect value for Exit on developer mode URL configuration option

SHIOS-2158: Changes in the ShieldSDK framework message in simulator builds

Description: Whenever an application calls App Shielding APIs (setting up callbacks etc) in a simulator, App Shielding will display the following log message:

---
☠ Shield is disabled in simulator builds ☠
---

When the app is unshielded and running in a real device, the ShieldSDK will print the following log message:

---
☠ Application is not fully shielded ☠
---

SHIOS-2419: Detect weakly linked ShieldSDK library

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

ARM64E limited support

External screen block

Blocking external screens (e.g. AirPlay) is currently not working for apps that use UISceneDelegate in iOS 13 and later.