---
title: "FieldBuddy Swift Update required before May 11, 2026"
canonical: "https://help.fieldbuddy.com/space/FBDOCS/blog/6855426066/FieldBuddy%20Swift%20Update%20required%20before%20May%2011%2C%202026"
format: markdown
---
> ⚠️ Recently Salesforce [announced](https://partners.salesforce.com/pdx/s/pcnews/mandatory-security-updates-for-connected-apps-and-ecas-MCFBLDLDQ2TVDZFA22GLAMBVEZGY?language=en_US) strengthening the security posture for all Connected Apps (CAs) and External Client Apps (ECAs) to ensure the highest level of trust and protection for our mutual customers. That has the impact to FieldBuddy Swift mobile application as well. These changes take effect on **May 11, 2026**. To ensure users can continue using FieldBuddy Swift without interruption,  it is necessary to update the FieldBuddy Swift to the latest version from Appstore or PlayMarket (3.510.6 fast ring / 3.510.4 slow ring or above).

Salesforce is introducing mandatory [security changes](https://partners.salesforce.com/pdx/s/pcnews/mandatory-security-updates-for-connected-apps-and-ecas-MCFBLDLDQ2TVDZFA22GLAMBVEZGY?language=en_US) to how mobile apps authenticate with Salesforce platform. These changes take effect on **May 11, 2026**. To ensure your users can continue using FieldBuddy Swift without interruption, all users must update the FieldBuddy Swift app before this date to the latest version.

![image-20260430-090444.png](media://807ee387-fc47-48ac-95ab-7fe5c1dff23f)

Users can update the app through the standard App Store (iOS) or Google Play Store (Android) update process. We recommend communicating this deadline directly to your users and, where possible, enforcing the update through your organisation's mobile device management (MDM) policy if present (3.510.6 fast ring / 3.510.4 slow ring).

### What is changing

Salesforce is enforcing two new security standards for all connected mobile apps:

- **Refresh Token Rotation** — Salesforce will now issue a new session token each time the app refreshes a user's session in the background. This is a security improvement that limits the risk of session hijacking.
- **PKCE (Proof Key for Code Exchange)** — Salesforce now requires a stronger, more secure login flow for all mobile apps. This replaces the use of a static application secret with a dynamic, per-session proof.

These are Salesforce platform changes. FieldBuddy has already implemented full support for both in the latest version of FieldBuddy Swift. Links to the release notes:

- [3.510.6 fast ring / 3.510.4 slow ring](https://help.fieldbuddy.com/page/fieldbuddy-fast-ring?released=changelog~post~fast-ring-fieldbuddy-swift-3-510-6-release)
- [3.511.0 fast ring / 3.510.6 slow ring](https://help.fieldbuddy.com/page/release-notes?released=changelog~post~fieldbuddy-swift-3-510-6-release-28-apr-2026)

(Please note that release notes are only for fast ring. But necessary security changes are also applied for the slow ring in the given version)

### What happens if users do not update

Users who are still on an older version of FieldBuddy Swift after May 10 will experience the following - their session will fail to refresh, they will be logged out, and will not be able to log back in until the app is updated.

There is no action required for the administrators / back office. Those are not impacted. The only requirement is that **all users update the FieldBuddy Swift application to the latest version**. Otherwise the changes that were done but not synced to the Service Center might get lost.

### Questions or Concerns?

If you have any questions or require assistance, please log a support ticket via our support portal. Our team will be happy to help.