This is a really important message about something. It could be about anything we deem important enough to tell everyone. It might have links to places, but shouldn't have any images or non-text content. Messages shouldn't be longer than two lines on normal sized layouts.
Genesys Cloud Developer CenterGenesys Cloud Developer Center
Browser storage is disabled

Your theme selection will not be remembered when you refresh the page. Please enable browser storage in the Account Switcher above to allow this setting to be remembered.

Topics
Analytics & Data Management
Authorization
Billing
Communication & Digital Channels
Overview
Journey
Collaborate Chat
Digital messaging and engagement
Digital messaging and engagement
Co-browse
Screen share
Web Chat
Digital Messaging Recipient Identifiers Messaging Media Uploads
Open messaging
Web messaging and Messenger
Web messaging and Messenger Authenticated web messaging APIs
Messenger JavaScript SDK
Content Security Policy Authenticated web messaging Web messaging Guest API
Mobile Messaging
Overview
Messenger Mobile SDK
Messenger Transport Mobile SDK
Support Policy
Web Deployments APIs WebMessaging APIs
External Contacts
Fax Greetings
Task Management in Work Automation
Textbots
Third Party Email and Chat Routing
Voicemail
GDPR & Privacy
Notifications & Alerts
Organization
Platform
Routing & Conversation Handling
Telephony
User & Agent Management
Resources
Announcements
AppFoundry
Genesys for Builders - Amazon Web Services Developer Blog Blueprints Changelog
Developer Applications
Developer Guides Videos
Home
|Communication & Digital Channels
|Digital messaging and engagement
|Web messaging and Messenger
|Mobile Messaging
Removed from toolbox

Support Policy

Versioning Policy

Mobile Messenger SDK and Transport SDK are versioned following the semantic versioning standard.

This standard helps convey the significance of changes in each new release based on a three-component version number, MAJOR.MINOR.PATCH. The version component incremented in a release depends on the changes introduced.

  • MAJOR version change happens when we make incompatible API changes other breaking changes, or introduce feature improvement that indicates a Major version upgrade
  • MINOR version change happens when we add functionality in a backward-compatible manner
  • PATCH version change happens when we make backward compatible bug fixes.
  • PRE-RELEASE - A pre-release version may be denoted by appending a hyphen immediately following the patch version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. Example: 2.7.2-rc1

Support Policy

When a new Major SDK version (N) is released, the previous SDK versions (N-1, N-2, etc.) remain available but become deprecated.

  • For N-1 SDK version: we do not perform regular QA testing, but we do allow customers to raise cases via Genesys Care: if Case investigation confirms defect, any hotfix would be provided on the latest Major Version only.
  • For N-2 and earlier SDK versions: Genesys Care tickets can be opened for older versions, but customers will be requested to upgrade to the latest version to see if the issue still occurs.

Example

  • Current Version is 4.2.0
  • Defect found in Version 3.1.0
  • Patch provided in Version 4.2.1
Genesys Cloud resourcesBeyond TrainingCommunity ForumKnowledge NetworkResource CenterStatus
App FoundryOverviewAvailable AppsContributeStyle Guide
Connect with usGithubTwitterDeveloper ForumDeveloper BlogGenesys BlogDevCast Newsletter
Copyright © 2025 Genesys. All rights reserved.
Terms of Use | Privacy Policy
On this page

Privacy Settings

This site uses cookies and related technologies, as described in our privacy policy, for purposes that may include site operation, analytics, enhanced user experience, or advertising. You may choose to consent to our use of these technologies, or manage your own preferences. Learn more here