Genesys Cloud – Deprecation: Mobile transport SDK capabilities

Genesys is updating several Mobile Transport SDK capabilities to improve security, platform compatibility, and API reliability. These changes increase the minimum supported operating system versions, introduce encrypted token and session storage, replace loosely typed APIs with typed alternatives, and reduce the public API surface by removing internal or unused symbols that were not intended for external use.

What is being deprecated?

As part of this change:

• The minimum supported operating system versions increase to Android 7/API 24 and iOS 15.
• TokenStore, DefaultTokenStore, and DefaultVault are deprecated in favor of the encrypted Vault implementation.
• FileUpload is deprecated in favor of FileAttachmentProfile.
• Message.type is deprecated in favor of the Message.messageType enum.
• Action is deprecated in favor of ButtonResponse.
• Direct use of Card is replaced by accessing cards through Message.cards.
• Internal or unused public symbols, including ErrorMessage, DEFAULT_PING_INTERVAL_IN_SECONDS, and String.sanitizeSensitiveData(), are removed or restricted from public use.

These changes provide more secure storage, improve type safety, and ensure that the SDK public API contains only functionality intended for customer use

Am I affected?

You are affected if you use the Mobile Transport SDK and plan to upgrade to a newer 3.x.x version that enforces these changes.

You are also affected if your application:

• Targets an Android version earlier than Android 7/API 24 or an iOS version earlier than iOS 15.
• Uses TokenStore, DefaultTokenStore, or DefaultVault.
• Uses FileUpload or Message.type.
• Directly references Action, Card, ErrorMessage, DEFAULT_PING_INTERVAL_IN_SECONDS, or String.sanitizeSensitiveData().
• Depends on modules or APIs that are removed as part of these changes.

Existing published applications will not automatically stop working on the end-of-life date. However, future builds using an updated SDK may fail if the application continues to target unsupported operating system versions or references APIs that have been removed.

How can I prepare for this deprecation?

Before upgrading to a Mobile Transport SDK version that enforces these changes, Genesys recommends that you:

• Set the Android minSdkVersion to 24 or later and the iOS deployment target to 15.0 or later. Update any corresponding Gradle, Podfile, project, and CI/CD configurations.
• Assess how ending support for older operating system versions and devices affects your users.
• Replace TokenStore, DefaultTokenStore, and DefaultVault with the encrypted Vault implementation and remove obsolete modules from your dependency configuration.
• Replace FileUpload with FileAttachmentProfile.
• Replace uses of Message.type with the Message.messageType enum, including related business logic, serialization, analytics, mocks, and tests.
• Replace Action with ButtonResponse and access cards through Message.cards.
• Remove dependencies on ErrorMessage, DEFAULT_PING_INTERVAL_IN_SECONDS, and String.sanitizeSensitiveData().
• Perform a clean build and test fresh installation, application upgrade, authentication, session restoration, file upload, attachment handling, and all applicable message-type flows before releasing the migrated application.

Existing applications can continue to operate after the end-of-life date, but these migrations must be completed before upgrading to an SDK release in which the deprecated capabilities are removed or no longer supported.

What if I need help or have questions?

If you need assistance preparing for this change or migrating your Mobile Transport SDK integration, contact your local Genesys representative or My Support.