After a client—via a connected app—receives an access
token, it can use a refresh token to get a new session when its current session expires.
The connected app’s session timeout value determines when an access token is no longer valid and
when to apply for a new one using a refresh token.
The refresh token flow involves these steps.
Mobile SDK apps can use the SmartStore feature to store data locally for offline use.
SmartStore data is inherently volatile. Its lifespan is tied to the authenticated user as well
as to OAuth token states. When the user logs out of the app, deletes all soup data associated
with that user. Similarly, when the OAuth refresh token is revoked or expires, the user’s
app state is reset, and all data in SmartStore is purged. Carefully consider the volatility of
SmartStore data when designing your app. This warning is especially important if your org sets a
short lifetime for the refresh token.
j