Ti.Cloud.currentUser() returns null when offline – how to preserve session for low‑traffic workloads?

Answer the question first

When a Titanium app goes offline, Ti.Cloud.currentUser() often returns null because the SDK can no longer validate the cached session token. The token is stored in the device’s secure storage; if it has expired or been cleared, the SDK treats the user as unauthenticated. This behaviour is consistent on both iOS and Android and is by design – the SDK does not attempt to refresh a token without network access.

Why the null result is expected in offline mode

• The Cloud API relies on a bearer token that is issued at login and has a TTL defined in the Cloud console.
• When the device loses connectivity, the SDK cannot reach the Cloud to confirm the token’s validity.
• If the token’s expiration time is in the past or the token was explicitly removed, currentUser() returns null.
• Both platforms use the same abstraction layer, so the behaviour is identical across iOS and Android.

Steps to preserve a session for low‑traffic workloads

1. Check the token’s expiration. Immediately after a user logs in, log the value returned by Ti.Cloud.getSessionToken() and the token’s expiry timestamp (available in the Cloud console under the user’s session details). Example:

   Ti.Cloud.getSessionToken(function(e) {
     if (e.success) {
       Ti.API.info('Session token: ' + e.sessionToken);
       // Store the expiry time if the API provides it
     } else {
       Ti.API.warn('No cached token');
     }
   });

2. Store the token yourself for quick reuse. After login, persist the token and its expiry in Ti.App.Properties. Use encryption if the token is sensitive:

   // Example – simple base64 encoding (not secure for production)
   var token = Ti.Cloud.getSessionToken();
   Ti.App.Properties.setString('cachedSession', btoa(token));
   // Store expiry as a timestamp
   Ti.App.Properties.setDouble('sessionExpiry', Date.now() + 3600 * 1000); // 1 hour TTL
   

3. Validate before using the SDK. On app launch, read the stored token and expiry. If the current time is before sessionExpiry, set the token back into the SDK (if a setter exists) or rely on currentUser() which will now return the cached user. If the token is missing or expired, trigger a re‑authentication flow.
4. Reduce Cloud traffic. Avoid calling Ti.Cloud.currentUser() in a tight loop. Cache the result in a local variable and use it for the duration of the session.
5. Test session expiry handling. Temporarily set a very short session timeout in the Cloud console (e.g., 5 minutes) and observe when currentUser() turns null. This confirms that TTL, not connectivity, is the root cause.

Diagnostic question

To fine‑tune the recommendation, could you tell me whether you have a custom session timeout configured in your Cloud console? The default timeout is 24 hours, but a shorter timeout would explain rapid token expiration during low‑traffic periods.