What's New in Mobile SDK 13.2

Mobile SDK 13.2 is a minor release that enhances authentication flexibility, enabling developers to seamlessly support multiple environments, roll out new scopes, and dynamically manage OAuth configurations.

In interim releases, we often deprecate items in native libraries for removal in an upcoming major release. Be sure to check your compiler logs for deprecation warnings so that you can address any changes before they go into effect.

These changes apply to more than one platform.

We no longer require apps to statically define OAuth scopes in their boot config file. If you don't specify a list of scopes, the client automatically uses server-defined scopes, and users are granted all configured scopes from the external client app or connected app. See Scope Parameter Values.

You can now dynamically override the consumer key, redirect URI, and scopes at runtime based on the login host the user selects. See Runtime Consumer Key.

Apps can now seamlessly migrate an active user's refresh token to a new OAuth configuration without requiring logout and login. This mechanism supports the controlled and incremental adoption of new OAuth settings, such as migrating from standard opaque tokens to JWT-based access tokens or transitioning from a connected app to an external client app. See Refresh Token Migration.

We created a sample app called AuthFlowTester, which you can use to test the authentication APIs added in Mobile SDK 13.2.

• Cordova command line: 13.0.0
• npm: 10.0 to latest
• Node.js: 20.0 to latest LTS
• React Native: 0.81.5
• React: 19.1.0

See also: General Updates in Mobile SDK 13.2.

You can now clear the WebView cache from the login screen’s settings menu on iOS.

Check your compiler warnings, or see iOS Current Deprecations.

See also: General Updates in Mobile SDK 13.2.

You can now use biometric authentication with native login on Android.

• Gradle: 8.14.3
• Android Gradle Plugin: 8.12.0

Check your compiler warnings, or see Android Current Deprecations.