Field Service Mobile

⚠️🔒 Important Notice about Enhanced Protection for Your Field Service Mobile Data 🔒⚠️

Hello Trailblazers,

We’re enhancing security for the Salesforce Field Service mobile app to better protect your sign-in tokens—the credentials that keep your mobile workers securely connected to Salesforce. These updates help defend your data against unauthorized access, stolen tokens, and token replay. The security enhancements will roll out automatically, but preparing early will ensure uninterrupted service for your mobile workforce. Here’s what you need to know and how to prepare.

What’s Changing

Two key security features that will work together to protect your mobile data:

• Refresh Token Rotation (RTR): RTR issues a new sign-in token each time the app authenticates, ensuring that compromised tokens become invalid almost immediately. This feature is available in the Salesforce Field Service Mobile App v264.1 (Winter ‘27) and will be enforced on January 18, 2027. All user devices must be updated to v264.1 or later by this date. After this date, older versions will experience periodic logouts. Note: Because signing out clears local data from the device, any unsynced work will be permanently lost.

• 30-Day Idle Sign-In Limit: Idle sign-in tokens now expire after 30 days of inactivity. Salesforce automatically applies this setting via the Connected App configuration Limit Idle Refresh Token Time-to-Live (TTL) to 30 Days. As long as a device connects to Salesforce at least once every 30 days, the user remains signed in and the 30-day window resets.

Key Dates 

• October 14, 2026: Field Service v264.1 begins roll out to the Apple App Store and Google Play for device updates
• October 21, 2026: 30-day idle limit rollout begins for Sandbox orgs
• November 4, 2026: 30-day idle limit rollout begins for Production orgs
• January 18, 2027: Enforcement deadline to update to v264.1 or later

Important Considerations for Field Service Mobile

Because mobile workers frequently operate in offline environments, plan around the following behavior:

• Re-authentication clears unsynced data: If a device goes unused for more than 30 days, the user must log in again when reconnecting. Re-authenticating in the Field Service mobile app clears any unsynced data remaining on the device. Unsynced data cleared during re-authentication cannot be recovered.
• Best Practice: Ensure all mobile devices connect and sync at least once every 30 days. Instruct mobile workers to sync pending work prior to going offline for extended periods to ensure they don’t lose data.

Device Support and Next Steps

No device support is dropped in the v264 (Winter ‘27) release. Devices currently in active use require no hardware upgrades or special action for the idle limit. The simplest way to maintain peak performance and to keep your data protected is to keep your Field Service mobile app current.

Next Steps

Plan your mobile app update cycle following the release of v264.1 scheduled for October 14, 2026, and ensure all user devices are updated prior to the January 18, 2027 enforcement date.

Going Forward

Ensure all mobile devices connect and sync at least once every 30 days. Sign-in tokens will now expire after 30 days of inactivity. Unsynced data will be permanently lost.

Help and downloads

• Release note: Refresh Token Idle TTL Is Limited to 30 Days
• Release notes: Field Service Mobile Winter ‘27
• Download for iOS: Apple App Store
• Download for Android: Google Play Store
• Questions: Salesforce Support

Dear all, 

We have observed that Work Plans and Work Steps do not appear immediately in the mobile application when the technician accesses them on their phone. 

A page refresh is required for them to be displayed. 

Work Plans and Work Steps are automatically generated when the Service Appointment status is changed to "On Site", and they should be displayed automatically without requiring a page refresh. 

The following screen shots show the before and after manual refresh :  

Before manual refresh :

After manual refresh : 

We have observed this issue since the deployment of Patch nr.2 of version 262

. 

We would be interested to know whether other customers have also experienced this issue in their Salesforce orgs.

Regards, 

Aur

📣 Field Service Mobile 262.3.1 Release Update [09/23/26] 📣

Hello Trailblazers! 

The latest patch for the Field Service Mobile app [iOS 262.3.1, Android 262.3 e-patch] has been released as of September 23rd, 2026, and is now rolling out in the App Store and Google Play. 

Here's a link to the release notes for details on major changes: 

Bug Fixes and Changes: 

Performance and battery improvements (iOS) 

- We fixed an issue where the app could gradually slow down and use extra battery the longer it was used during a shift. The slowdown built up over time, and was most noticeable when workers moved back and forth between work orders and ran flows or entered data. The app now releases background work it no longer needs, so performance and battery use stay steady throughout the day. 

Offline PDF sync fix (iOS and Android) 

- We fixed an issue where offline Service Reports and checklist PDFs could fail to sync, returning an "Enter a valid record ID" error. 

Note: 

We deploy major and patch releases over several days to ensure stability. The updates aren't necessarily available for all users until 7 days after the app becomes generally available.

📣 Field Service Mobile 262.3 Release Update [09/04/26]📣 

Hello Trailblazers! 

The 262.3 patch for the Field Service Mobile app [iOS 262.3.0, Android 262.3.19] has been released. Beta became available on August 26th, 2026, and the update is now rolling out to production in the App Store and Google Play. 

As always, we encourage your feedback. Here's a 

document with recommendations on how to test beta builds, and a document

 on how to provide feedback — please raise any 

critical issues immediately 

Bug Fixes and Changes: 

iOS 

1. Fixed an issue where Lightning web components could become inconsistent while priming or viewing them. 

2. Improved app startup reliability — the startup watchdog no longer counts time spent suspended in the background, preventing false timeouts and unnecessary restarts. 

3. Fixed an issue that could unexpectedly log users out after the app was suspended in the background; the app now retries loading org settings instead. 

4. Fixed "check for updates" incorrectly reporting no update available due to a stale cache, which could suppress the update prompt for 24+ hours. 

5. Additional stability improvements to the Lightning SDK. 

Android 

1. Fixed a crash that could occur when reading the cached bootstrap manifest on launch. 

2. Fixed a crash during web-server authentication login. 

3. Fixed an OAuth login issue where users could get stuck in the in-app browser (Custom Tab) during sign-in. 

Note: We deploy patch releases over several days to ensure stability. Updates aren't necessarily available to all general availability. 

Here's a link to sign up for the 

beta program.

If anyone Have a Documentation regarding this then reply