Salesforce ships Field Service Mobile Patch 2 on July 29, deprecates Android 12
Salesforce released Field Service Mobile Patch 2 to general availability on July 29, 2026, with the update arriving in a staggered rollout and Android 12 support discontinued for the mobile app. Salesforce lists the GA timing on its Field Service Mobile App Updates calendar, and the July ’26 monthly notes confirm Android 12 support is discontinued.
Field Service Mobile Patch 2 GA on July 29, 2026
Patch 2 moved from beta on July 22 to GA on July 29, with Salesforce reminding admins that mobile updates can take up to a week to reach every device. That seven‑day window is called out in the mobile release cadence guidance, so fleet owners should expect mixed client versions in the field during the rollout.
Android 12 support ends as Salesforce raises the mobile baseline
The July ’26 notes state that the Field Service mobile app now requires Android 13 or later, ending official support for Android 12 and older as part of Summer ’26. That change is reiterated on the umbrella Field Service pages covering mobile changes, including the item “Field Service Mobile App Support on Android 12 Is Discontinued,” which is referenced under the main Field Service Mobile updates.
What enterprise IT teams should do this week
- Confirm OS compliance: Inventory technician devices and validate that Android units are on 13+ before enabling forced updates. Salesforce’s release calendar notes that updates propagate over several days, so lock versions in MDM if you need a brief testing holdback per the GA rollout guidance.
- Re-check app requirements: Review your supported mobile OS plan against Salesforce’s published technical requirements and support schedule to avoid falling more than one major platform release behind.
- Validate critical flows offline: In practice, minor mobile patches can surface edge cases in offline briefcases and custom flows. Run a smoke test on work order updates, parts usage, and signature capture before pushing to all crews.
Why this patch matters for Field Service operations
For large fleets, even a “patch” triggers real work: verifying device OS posture, coordinating MDM waves, and ensuring briefcase priming still behaves under the new client. The combination of a time-boxed GA window and a higher Android baseline means organizations with rugged devices or long replacement cycles should prioritize a quick readiness check using Salesforce’s July ’26 release notes summary as their source of truth.
Share With Others
Platinum
