Summary
Version 3.0.0 of the Genesys Mobile Messenger SDK and Mobile Transport SDK, planned for October 27, 2026, introduces several breaking changes. These include consolidation of the Android and iOS Mobile Messenger SDK modules, migration of SDK artifacts to new repositories, increases to minimum supported OS and API versions, and removal of deprecated APIs from the Transport SDK.
Applications already deployed to production will not be affected when version 3.0.0 is released. Action may be required when customers rebuild an existing application or upgrade to version 3.0.0 or later.
Effective Date
Tuesday, October 27, 2026
Details
Module Consolidation (Android and iOS)
The Mobile Messenger SDK versions 2.X.X consist of three separate modules:
iOS:GenesysCloud, GenesysCloudMessenger, and GenesysCloudCore.
Android: core (com.genesys.cloud), chatintegration (com.genesys.cloud.integration), and ui (com.genesys.cloud.ui).
To support communication across these modules, numerous internal APIs were exposed as public, resulting in a broad and complex public API surface.
With the release of version 3.0.0, these three modules are being consolidated into a single GenesysCloud module. This allows the public API surface to be optimized by restricting APIs intended only for cross-module communication to internal visibility.
A comprehensive list of deprecated APIs scheduled for removal in 3.0.0 is available in the Developer Center.
Any new cross-module APIs introduced before 3.0.0 will be marked as deprecated upon release and will have their public visibility removed in 3.0.0.
Artifact Repository Migration (Android and iOS)
Starting with version 3.0.0, SDK artifacts will be published to new locations. The legacy artifact repository will be decommissioned.
Android: Artifacts are moving to Maven Central under a new group ID.
iOS: Binaries are moving to GitHub Releases.
Minimum OS/API Version Increases
- Mobile Messenger SDK (Android): minimum API level raised from 21 to 24 (Android 7.0)
- Mobile Transport SDK (Android): minimum API level raised from 21 to 24 (Android 7.0)
- Mobile Transport SDK (iOS): minimum deployment target raised from iOS 13 to iOS 15
Transport SDK Legacy API Removals
Version 3.0.0 removes a number of deprecated APIs from the Mobile Transport SDK, including storage, messaging, and internal utility APIs that have been superseded by newer alternatives.
The Transport SDK's ktor networking dependency will also no longer be exposed transitively.
For the full list of affected APIs and migration guidance, see the Transport SDK Deprecations page.
Customer Impact
There is no immediate impact to applications already deployed to production when version 3.0.0 is released. Customers may need to take action in the following situations:
When rebuilding an existing application, dependency configuration may need to be updated to retrieve SDK artifacts from their new locations.
When upgrading to version 3.0.0 or later, code changes may be required depending on which SDK APIs the application currently uses.
Module Consolidation:
Review the full list of deprecated APIs targeting removal in 3.0.0 and update any usages before upgrading.
If your application uses only the documented public APIs, no code changes are expected as a result of the module consolidation.
Artifact Repository Migration:
Android: When rebuilding or upgrading, update your build.gradle:
- Replace the legacy repository URL with mavenCentral().
- Change the dependency group from com.genesys.cloud to cloud.genesys for all SDK artifacts.
This is a one-time dependency configuration change.
iOS:For version 3.0.0 and later, no action is needed because package specifications already point to the new location. For older versions (1.13+):
- CocoaPods: run pod update.
- SPM: re-resolve packages in Xcode under File → Packages → Resolve Package Versions.
Minimum Version Increases:
Before upgrading to version 3.0.0, ensure your application targets at least:
Android API level 24 (Android 7.0) when using the Mobile Messenger SDK or Mobile Transport SDK for Android.
iOS 15 when using the Mobile Transport SDK for iOS
Transport SDK API Removals:
Review the Transport SDK Deprecations page for the full list of removed APIs and their replacements before upgrading to version 3.0.0.
If your application uses ktor-client-okhttp directly, add it explicitly to your own build.gradle:
implementation("io.ktor:ktor-client-okhttp:x.x.x")
Impacted Resources
- Mobile Messenger SDK for Android
- Mobile Messenger SDK for iOS
- Mobile Transport SDK for Android
- Mobile Transport SDK for iOS
- Android Maven artifact group com.genesys.cloud → cloud.genesys
- iOS CocoaPods and SPM package sources
Explanation
The module consolidation reduces the number of APIs that must be maintained as public contracts, simplifies the SDK integration experience, and allows the team to evolve the SDK's internal architecture without unnecessarily impacting customers.
The artifact repository migration is required because the legacy repository is being decommissioned and will no longer be available.
The minimum version increases align with current platform toolset recommendations and allow the SDKs to take advantage of modern Android and iOS capabilities while reducing maintenance overhead for legacy OS versions.
Transport SDK API removals eliminate previously deprecated APIs that have been superseded by newer alternatives, keeping the supported public API surface focused and maintainable.
Issue References
- GMMS-14342
- GMMS-15318
- GMMS-14542
Contacts
@Anton Afanasiev @David Kempl @Kalman Perkel Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.