Repository navigation
1.8.0
Major Release: Messaging for In-App (Android)
Enhance the Messaging for In-App experience with the new Messaging for In-App features. Improve the user experience by auto-populating the pre-chat form fields, selecting the preferred browser type for opening rich links, and much more.
To learn more, see the Messaging for In-App Developer Guide.
This page covers the Android release notes. For iOS, see the iOS release notes.
New Features
- Added the ability to end the current session on a conversation.
- Added displaying a configured fallback message when entering the conversation.
- Added markdown support to inbound text messages.
- Added a new UI experience for typing indicators.
- Added an optional opt out flag for the agent experience of the new typing indicator UI to distinguish between humans and bots.
- Added support for AgentForce bot progress updates to manage end user's expectation for loading response time.
- Added support for sending and receiving several new file types including CSV, XML, TXT, WORD files and Excel spreadsheets.
- Added support for streaming AgentForce text messages. Allows the end user to receive messages as they are being generated in real-time.
API Changes
- Added
conversationClient.endSession(). This call will end the session on the conversation. - Added the
FallbackMessageconfiguration to the RemoteConfiguration object. - Added the
Participant.roleTypefield of typeParticipantRoleType(Enum) to replace theParticipant.roleString?. Possible enum values are:Agent, Chatbot, EndUser, System, Unknown, Supervisor, Router; - Deprecated
Participant.role. Use theroleTypeEnum instead. - Added a new configuration object
UIConfiguration.agentConfigurationwith an option to opt out of the new progress indicator experience for agents.
Bug Fixes
- Fixed an issue where calling
CoreClient.clearStorage()could lead to unexpected results ifCoreClient.Factory.destroy()was not also called. - Fixed an issue where providing a limit of
0on any conversation/conversation entry list API would return 0 results from the database. Providing a limit of 0 will query the database with a limit of -1 instead. - Fixed a crash when using deep links (custom scheme) in a enhanced link messaging component.
- Fixed an issue where deep links were not rendering for some message types.
- Fixed an issue where PDF pager background in dark mode was making the content hard to read.
- Fixed an issue where re-registering for push notifications would have no affect until the app was restarted.
Known Issues
- URI links are not automatically parsed from a block of plain text. This is a platform difference between iOS and Android. There are two main workarounds for this:
- Use an explicit link message type (richlink or webview messaging component)
- Use the new markdown support to provide the link
[link](mydeeplink://path)
Notes
- Updated Android Compose BOM to 2025.01.01 / 1.7.7 (strictly >= 1.7.0 < 1.8.0)