Genesys Cloud – Deprecation: Mobile messenger SDK v3.0 module consolidation and API
| Type | Impact | Action required | Audience | Community link | Aha! link | Announced on (YYYY-MM-DD) | Planned effective date (YYYY-MM-DD) |
|---|---|---|---|---|---|---|---|
| Deprecation | — | — | — | — | — | 2026-09-14 | 2026-10-31 |
With the release of Mobile Messenger SDK version 3.0.0, Genesys is simplifying the Mobile Messenger SDK by consolidating the existing SDK modules into a single module and reducing the public API surface. These changes make the SDK easier to use, maintain, and support.
What is being deprecated?
Mobile Messenger SDK version 2.x consists of three separate modules:
- GenesysCloud
- GenesysCloudMessenger
- GenesysCloudCore
To enable communication between these modules, many internal APIs were exposed as public APIs. With SDK version 3.0.0, these three modules are consolidated into a single GenesysCloud module.
As part of this change:
- The GenesysCloudMessenger and GenesysCloudCore modules are deprecated and removed.
- Several internal SDK APIs that were previously public are removed or restricted to internal use.
- Android SDK artifacts move from the JFrog repository to Maven Central.
- iOS SDK binaries move from the previous distribution method to GitHub Releases.
These APIs and modules will not be replaced.
Am I affected?
You are affected if you use Mobile Messenger SDK version 2.x for Android or iOS and plan to upgrade to version 3.0.0.
You are also affected if your application:
- References the GenesysCloudMessenger or GenesysCloudCore modules.
- Uses any of the deprecated internal SDK APIs that are removed in version 3.0.0.
- Retrieves Android artifacts from the JFrog repository.
How can I prepare for this deprecation?
Before upgrading to Mobile Messenger SDK version 3.0.0, Genesys recommends that you:
- Remove the deprecated GenesysCloudMessenger and GenesysCloudCore modules from your Gradle or CocoaPods configuration.
- Update your 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 your application for any use of deprecated internal SDK APIs and remove those references before upgrading.
These changes streamline the SDK and reduce the exposed API surface by removing implementation details that were never intended for customer use.
A complete list of the breaking API changes is available in the SDK migration documentation.
What if I need help or have questions?
If you need assistance preparing for this change or migrating to Mobile Messenger SDK version 3.0.0, contact your local Genesys representative or My Support.
[NEXT] Was this article helpful?
Get user feedback about articles.