Genesys Cloud – Mobile Messenger SDK version 3.0.0 module consolidation and distribution changes
| 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 Messenger SDK version 3.0.0 with a consolidated module structure and updated distribution methods for Android and iOS. The new version combines the GenesysCloud, GenesysCloudMessenger, and GenesysCloudCore modules into a single GenesysCloud module. Android SDK artifacts will move from the JFrog repository to Maven Central, and iOS SDK binaries will move to GitHub Releases.
These changes reduce the number of public APIs that exist only to support communication between separate modules and provide a simpler SDK structure for developers to work with.
Customers can continue to use their current Mobile Messenger SDK version. Upgrading to version 3.0.0 is optional.
What’s changing
With Mobile Messenger SDK version 3.0.0:
- Module consolidation – The GenesysCloud, GenesysCloudMessenger, and GenesysCloudCore modules will be consolidated into a single GenesysCloud module.
- Public API changes – APIs that were exposed to support communication between the separate modules will be removed or restricted to internal use.
- Android distribution – Android SDK artifacts will move from the JFrog repository to Maven Central.
- iOS distribution – iOS SDK binaries will move to GitHub Releases.
Why this matters
The current three-module structure requires Genesys Cloud to expose internal APIs so that the modules can communicate with one another. Consolidating the modules reduces the number of APIs exposed for internal SDK operations and gives developers a simpler public API surface to work with.
The distribution changes also move Android and iOS SDK packages to their new distribution locations.
What developers need to do
Customers who continue to use their current Mobile Messenger SDK version do not need to make changes.
Developers who choose to upgrade to Mobile Messenger SDK version 3.0.0 should:
- Remove the GenesysCloudMessenger and GenesysCloudCore modules from their Gradle or CocoaPods configuration.
- Update their project to use the consolidated GenesysCloud module.
- Update Android dependencies to retrieve SDK artifacts from Maven Central.
- Update iOS integrations to obtain SDK releases from GitHub Releases.
- Review their application for APIs that are removed or restricted in version 3.0.0 and update their code as needed.
[NEXT] Was this article helpful?
Get user feedback about articles.