Salesforce
| Start your FREE trial |
| Request a demo |
Welcome to Resco for Salesforce wiki.
Select one of the topics below or visit the Table of contents for a full list of categories and articles.
Important
This urgent, time-critical notice concerns only Resco customers who use the Resco Mobile CRM application with the Salesforce backend.
| Important | Resco is mandated to introduce a breaking change in the Resco Mobile CRM app to remain compliant with updated Salesforce security requirements for external connected apps. More information about these requirements can be found here: Secure Your Connected Apps and External Client Apps. |
Critical impact — immediate action required
The critical requirement for Resco customers using Resco Mobile CRM for their business is to ensure that all mobile devices are upgraded to Resco Mobile CRM 19.1.5 (or later) before July 30, 2026, 8:00 CET. As of this date, Resco is required to update its global connected app definition to comply with updated Salesforce security requirements. This means that, from this date onward, any earlier versions of Resco Mobile CRM will no longer be able to connect to Salesforce. Users will receive an error message whenever the application needs to authenticate with Salesforce.
There is no other requirement for customers to continue using Resco Mobile CRM beyond ensuring the app is upgraded. In case the deadline is missed and an older version of the app can no longer connect, upgrading it will resume communication. Unsynced local data will not be lost; however, Resco strongly recommends upgrading before the deadline to avoid business interruption.
Other impacts and notes
New mandatory security settings also require Resco to tighten refresh token-related policies, specifically forcing a frequent refresh token invalidation and setting the maximum token expiration to 30 days. In practical terms, users might experience the following behavior changes in the app
- App may ask the user more frequently to re-login, especially when using the same user account on multiple devices.
- When using the same user account on more devices, intermittent "invalid session" errors may occur during web communication (when syncing or in online mode).
- On very rare occasions, the "invalid session" web communication errors might appear even when single device is used. These are transient, and re-login or restarting the app will fix them. Please report these to Resco support.
The requirement for Allowlist ranges for Refresh Tokens doesn't apply to Resco Mobile CRM and won't be enforced.
