Genesys Cloud – Mobile Transport SDK version 3.0.0 platform and API updates
| Type | Impact | Action required | Audience | Community link | Aha! link | Announced on (YYYY-MM-DD) | Planned effective date (YYYY-MM-DD) |
|---|---|---|---|---|---|---|---|
| Platform | Medium | Planning Recommended | Developer | — | — | 2026-10-12 | - |
In a future release, Genesys Cloud will introduce Mobile Transport SDK version 3.0.0 with updated platform requirements, encrypted token and session storage, typed file and message APIs, and a reduced set of public SDK symbols. The new version will require Android 7/API 24 or later and iOS 15 or later. It will also replace several existing SDK capabilities with updated alternatives and remove or restrict internal and unused public symbols.
These changes improve the security of stored authentication data, provide more consistent APIs for working with files and messages, and remove public SDK elements that applications do not need to use.
Customers can continue to use their current Mobile Transport SDK version. Upgrading to version 3.0.0 is optional.
What’s changing
With Mobile Transport SDK version 3.0.0:
- Minimum operating system versions – Applications that upgrade must target Android 7/API 24 or later and iOS 15 or later.
- Token and session storage – Applications must migrate from deprecated token and session storage components to the encrypted Vault implementation.
- File and message APIs – Applications must migrate from deprecated file and message APIs to typed alternatives, including FileAttachmentProfile and Message.messageType.
- Public SDK symbols – Internal or unused public SDK symbols that were not intended for external use will be removed or restricted.
- Application code – Applications that use affected capabilities must update their code when they upgrade to version 3.0.0.
The existing deprecation content identifies applications that target operating system versions below Android API 24 or iOS 15, or that use deprecated APIs and modules, as the applications affected by these changes. Pasted text
Why this matters
Mobile Transport SDK version 3.0.0 stores authentication information using encrypted storage, replaces loosely typed APIs with typed alternatives, and removes public SDK elements that applications do not need. These changes provide clearer APIs for developers and update the SDK’s platform and security requirements.
What developers need to do
Customers who continue to use their current Mobile Transport SDK version do not need to make changes.
Developers who choose to upgrade to Mobile Transport SDK version 3.0.0 should:
- Update the Android minSdkVersion to API 24 or later and the iOS deployment target to iOS 15 or later.
- Remove deprecated modules from Gradle or CocoaPods configuration as applicable.
- Migrate deprecated token and session storage to the Vault implementation.
- Migrate affected file and message functionality to the documented typed APIs, including FileAttachmentProfile and Message.messageType.
- Review their application for other APIs or public symbols that are removed or restricted in version 3.0.0 and update their code as needed.
- Test affected authentication, session restoration, file upload, and messaging workflows before releasing the updated application.
[NEXT] Was this article helpful?
Get user feedback about articles.