When technicians attempt to log in to the Salesforce Field Service Mobile (FSM) app on certain Android devices, they may encounter a "Something went wrong" error and cannot proceed. The same user credentials work correctly on a different device, indicating the issue is device-specific rather than an account or permission problem.
Examining the FSM app log file reveals the following error sequence:
I/SalesforceSdkFacade: User logout received. Reason: CORRUPT_STATE_APP_PROVIDER_ERROR_INVALID_USER
W/BootstrapHostApp: Request Failed for /services/data/vXX.0/graphql?
com.salesforce.androidsdk.rest.RestClient$RefreshTokenRevokedException: Could not refresh token
Root Cause: Android manufacturers — particularly Vivo, Xiaomi, OnePlus, and similar OEMs — can restrict background app activity. When the FSM app's background OAuth token refresh process is killed by the battery manager, the stored credential state becomes corrupted. On the next login attempt, the Salesforce Android SDK cannot recover the user context, surfacing as "Something went wrong."
Affected Platforms:
Android devices with aggressive battery management (Vivo, Xiaomi, OnePlus, Oppo, and similar OEM builds)
Any FSM app version on Android 9+
Particularly common after the device has been idle overnight or after a power-saving mode activation
Perform both steps on the affected device:
Step 1 — Disable Battery Restriction for the FSM App
Settings → Apps → Field Service → Battery (exact path varies by manufacturer)
Set battery usage to Unrestricted (also labeled "No restrictions" or "Allow background activity")
Vivo: Settings → Battery → High Background Power Consumption → add Field Service
Xiaomi/MIUI: Settings → Apps → Field Service → Battery Saver → No Restrictions
Step 2 — Clear App Cache (Do NOT Clear Data)
Settings → Apps → Field Service → Storage
Tap Clear Cache only — do NOT tap "Clear Data" (this removes all offline briefcase content)
Close Settings, open Field Service, and attempt login again
If the Issue Persists:
Collect FSM app log (FSM app → Settings → Export Logs)
Search the log for CORRUPT_STATE or RefreshTokenRevoked to confirm the pattern
If a different error appears, contact Salesforce Support with the log attached
If the above steps don't resolve the issue, also verify the user has an active Service Resource record with correct sharing access before assuming it's device-specific.
005393410

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.