The "Enable Refresh Token Rotation" option is now checked by default on every newly created external client app. The setting is locked (grayed out), and customers cannot uncheck it themselves.
This issue impacts customer-built mobile apps that use Mobile SDK versions prior to 14.0 and authenticate against an External Client App (ECA) or connected app with refresh token rotation enabled. Because Refresh Token Rotation (RTR) is now enabled by default and locked on all newly created ECAs, any pre-MSDK 14.0 mobile app authenticating against a new ECA will be affected.
When a new ECA is registered and end users start authenticating against it from a mobile app built on a version prior to 14.0, these are the behaviors that appear shortly after:
Users are logged out of the mobile app more frequently than before.
Users are prompted to re-authenticate even though their session/refresh token should still be valid.
Background sync, offline actions, or push-triggered launches fail with authentication errors and force a fresh login.
For customer-built mobile apps that use Mobile SDK versions prior to 14.0 and authenticate against an External Client App (ECA) or connected app with refresh token rotation (RTR) enabled , it is critical that apps are upgraded now to ensure a smooth, gradual rollout and enough runway for users to move to the updated app, so that any new ECA doesn’t get impacted by RTR.
1. Upgrade your mobile app to Mobile SDK 14.0 as soon as possible.
2. Release the updated app to your end users through your normal distribution channel (App Store, Google Play, or MDM). To drive adoption, we recommend in-app messaging that notifies users when a newer version is available or a forced-update mechanism that requires users to update before continuing. This ensures your users move to the compliant build ahead of time rather than relying on them to update on their own.
3. Keep RTR enabled on your ECA — no further action needed.
OAuth Security Controls Are Enforced for New External Client Apps and Connected Apps
Upgrade to Salesforce Mobile SDK 14.0 to Avoid Service Disruption from Upcoming Security Mandates
005390912

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.