1.4.0

Release Notes: Messaging for In-App (Android)

Enhance the Messaging for In-App experience with new Messaging for In-App features. Customize the user experience based on your business hours, send and receive GIFs during conversations, use the conversation list to organize a group of distinct conversations, take advantage of dropdowns in pre-chat forms, and 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

• Improved message search embedded in the existing conversation options screen.
• Added support for Terms and Conditions:
  • Show the Terms and Conditions UI if it's enabled in the org.
  • Display a spannable string with parsed links.
• Added support for unknown conversation entries.
• Added right-to-left (RTL) support.
• Added support for secure forms.
• Use Branding Tokens and String Tokens for the Latest Features
  See Customize Colors and Customize Strings.

API Changes

• Changed API to submit entire remote configuration object instead of pre-chat fields only.
  • ConversationClient.submitRemoteConfiguration(remoteConfiguration: RemoteConfiguration): Result<Conversation?>
  • ConversationClient.retryEntry(conversationEntry: ConversationEntry,remoteConfiguration: RemoteConfiguration): Result<ConversationEntry>
• Updated Kotlin version to 1.8.
• New string tokens. See Customize Strings.
  • Terms and Conditions tokens: smi_terms_and_conditions_accept, smi_terms_and_conditions_error
  • Unkown conversation entry token: smi_unknown_entry_message

Bug Fixes

• Fixed an issue where the agent's attachments may disappear after scrolling the feed.
• Fixed an issue where tapping on a placeholder image would open the attachment viewer.
• Improved screen transition animations to better reflect the navigation action.
• Fixed an issue with the network banner where sometimes it would report no connection when transitioning between Wi-Fi and cellular.
• Fixed a crash caused by malformed templated URLs.
• Added missing branding tokens for the search input view and various chat feed breaks (participant changed, auto-response, etc.)

Known Issues

• If you want to enable Terms and Conditions during mid-conversation pre-chat, for example, to show them for every new session with an agent, go to the Pre-Chat Form settings page of your Embedded Service Deployments page in Setup. Then select Every Session for Pre-Chat Display Frequency and enable a hidden pre-chat field. To learn about and set up pre-chat, see Customize Pre-Chat for Messaging for In-App and Web.
• When a user uploads a file larger than the maximum file size (5 MB), the upload fails without a helpful error message. This is a known issue with the release version of the third-party library that we’re using (OkHttp). We’ll update the library when they release a fixed version.
• We don’t support implementing user verification alongside anonymous users. Your implementation must be designed for either verified users or unverified users.
• We support one deployment per app implementation. Workaround: You can enhance your Omni-Channel flow or send additional hidden pre-chat fields to accommodate multiple use cases from a single deployment.
• When logging in as a verified user (using User Verification), multiple devices can access the same conversation. However, when sending an image from one device, the other device won’t be able to see that image. They see a gray box in place of that image. Images coming from the agent are visible on all devices.
• When using the SDK in an app in the simulator, if you attempt to attach an image on the simulator by tapping the "Take a Photo" button, nothing happens. Workaround: Use a real device when testing the camera.
• If a customer sends a message with a URL that starts with a capital letter in the protocol (“Http” instead of “http”), the server incorrectly prepends an additional “http”.