Field Service Mobile App Updates

Stay in the know about the Field Service mobile app releases. This topic includes information on the mobile app release cadence for major, patch, and daily releases (also known as emergency releases), plus information on testing and beta periods.

Required Editions

Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
The Field Service core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions.
To access the Field Service mobile app, users need the Field Service Mobile user license.
Note
Note For users with the Access Lightning Web Components (LWCs) permission set, you must update the mobile app to ensure LWCs function properly. The app must be no more than two major releases behind the Salesforce platform for the app to continue to work with LWCs. For example, when your org updates to Summer '25, any versions from Summer '24 and earlier will stop working. Note that the Spring '24 release will reach its end of life early with the Winter '25 release. Additionally, you must update the app to the latest major version to access new features or bug fixes.

Release Maintenance Types

The Field Service mobile app has three types of releases, which align with Salesforce maintenance types: major releases, patch releases, and daily releases. So you can best prepare for changes, here’s a description for each type of release, including the length of their associated beta testing period.

Release Type Description Frequency
Major release Updates Salesforce Field Service mobile app with new features. The beta period is approximately 30 days. Three times per year
Patch release Deploys changes and fixes as needed to address significant, but nonemergency, customer impacting issues. The beta period is 7 days. As needed
Daily release (also known as emergency release) Deploys fixes to emergency customer-impacting issues as needed. No beta period, because daily releases are deployed on an emergency basis. As needed

Mobile Release Calendar and Communication

Here are the approximate dates for the next three major releases and patch releases. Release dates are occasionally delayed to maintain customer trust.

Release Beta Generally Available
Spring '26
Beta January 14, 2026 N/A
Major Release (Patch 1) February 25, 2026 March 4, 2026
Patch 2 April 8, 2026 April 15, 2026
Patch 3 May 6, 2026 May 13, 2026
Summer '26
Beta May 13, 2026 N/A
Major Release (Patch 1) June 17, 2026 June 24, 2026
Patch 2 July 22, 2026 July 29, 2026
Patch 3 August 26, 2026 September 2, 2026
Winter '26    
Beta September 2, 2026 N/A
Major Release (Patch 1) October 7, 2026 October 14, 2026
Patch 2 November 11, 2026 November 18, 2026
Patch 3 January 6, 2026 January 13, 2026
Note
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.

Timeline for Field Service Mobile App releases

Note
Note Use the current APK file for emergency installation during beta testing periods, and use the APK file from the previous release for emergency installation during major releases.

And here’s where and when you can find communication about each release.

Release Type Where When
Major release

Learn more about major releases and new mobile app features in our standard Salesforce Field Service release notes.

You also receive notification through your Trailblazer group.

Release notes offer a preview of new features approximately two months before the release. And you get notification via your Trailblazer group when beta and major releases go live.

Patch release Find information about patch releases through the Field Service Mobile Trailblazer group and on the Field Service Mobile Updates page.

When we identify a need, we inform you. You receive a second announcement when the release goes live, approximately 7 days later.

The first announcement includes a brief description of each issue resolved to help you focus your testing.

Daily release (emergency) Find information about daily releases through the Field Service Mobile Trailblazer group.

When we identify a need, we inform you at least a day before a daily release. You receive a second announcement when the release goes live.

Testing Best Practices

Test features before they’re generally available by using the Field Service Mobile Beta and Early Adopters Program. If you have issues with a beta version, log a case immediately so that it can be reviewed before the generally available (GA) release.

If you have complex security or compliance requirements and require greater control over what updates go out, you can use Mobile Device Management (MDM).