Version 5.0.3 (April 2023)
- 28 Oct 2024
- 2 Minutes à lire
- SombreLumière
Version 5.0.3 (April 2023)
- Mis à jour le 28 Oct 2024
- 2 Minutes à lire
- SombreLumière
The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article
Avez-vous trouvé ce résumé utile ?
Merci pour vos commentaires
Supported platform versions
App Shielding version 5.0.3 was successfully tested with Android 13.
Android 4.4 (API level 19) – Android 13 (API level 33).
Shielding Tool:
Windows 10: 64-bit Java 11 or 17
Mac OSX (10.9+)
Ubuntu Linux 20.04 LTS or 22.04 LTS
ShieldGradlePlugin version 2.0 and later are supported. ShieldGradlePlugin version 2 supports Android App Bundles and newer Android build versions.
The Android Native Development Kit (NDK) r24 stopped support of Jelly Bean (API 16, 17, and 18). The minimum version supported by the NDK for r24 and later is KitKat (API level 19). App Shielding has switched to Android NDK r25.
Android platform updates
The Android minimum supported version is 4.4 (API level 19).
As of July 1, 2022, App Shielding for Android version 4.2.0.39971 and earlier are no longer supported. For more information, refer to the OneSpan Customer Portal.
New features and other updates
Changed naming scheme for bound package
As of version 5.0.4, we will change the naming schema of the bound package contained within a .zip file. The file name prefix will change from “wrapped” to “shielded”.
Old naming schema:
wrapped-original package file name.original package file extension
New naming schema:
shielded-original package file name.original package file extension
Fixes and other changes
RASP-3389: Shielding Tool loads application signer certificate
Description: The Shielding Tool can now load the application signer certificate from the apk if the app is signed with APK Signature Scheme 2 or 3 and no longer has the v1 Scheme Signature. The v1 Scheme Signature is no longer added for a default Android Studio project with minSdkVersion > 24. The APK signature is used in the App Shielding repackaging check when the application is configured with applicationSignerCertificateauto (this is the default) or original.
Example:
--- <?xml version="1.0" encoding="UTF-8"?> <shield> <config> <applicationSignerCertificate v="auto" /> <applicationSignerCertificate v="original" /> ... </config> </shield> ---
For more information, refer to https://source.android.com/docs/security/features/apksigning.
SHAND-3416: Fix unexpected termination on Android 4.4
Description: App Shielding sometimes terminated unexpectedly on Android 4.4 because an internal App Shielding Java class was not available from the first classes.dex file.
Status: This issue has been fixed. This fix is only recommended if your application supports Android 4.4.
SHAND-3476: Fix unexpected termination on application start on Android versions 7 and earlier
Description: Some applications are optimized by R8 in Application.attachBaseContext() which causes a shielded application to terminate unexpectedly upon starting the application. This unexpected termination happens only on Android versions 7 and earlier.
Status: This issue has been fixed. Now the Shielding Tool can handle R8-optimized Application.attachBaseContext() correctly.
Known limitations
The limitations described here have not yet been solved for the current Mobile Application Shielding version. Possible workarounds are described where available.
Android App Bundles
The OneSpan Customer Portal support for Android App Bundles does not yet include instant-enabled app bundles.
Detection of root hiding tool on new Android versions
Due to the nature of root hiding tools and the increasing restrictions Android imposes on applications as of Android 9, OneSpan Mobile Application Shielding may not be able to reliably detect a rooted device that uses root hiding tools.
Cet article vous a-t-il été utile ?