1.3.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

• Set Business Hours in Messaging for In-App and Web
  The UI SDK automatically shows a banner to customers during business hours letting them know that your business hours are over. For both UI SDK and Core SDK apps, you can use the API to prevent incoming conversations outside of business hours. See Business Hours in the Messaging for In-App developer guide.
• Use Conversation Lists to Show Customers Multiple Conversation Threads
  See Conversation Lists in the Messaging for In-App developer guide.
• Send and Receive GIFs During Conversations
• Add a Bot Options Menu to the Chat Window
  The UI SDK automatically displays the bot options menu. To access the menu with the Core SDK, use the Participant.clientMenu property.
• Let Messaging for In-App and Web Conversations Continue Across Multiple Channels
  Learn more about User Verification in Salesforce Help.
• Add Dropdown Fields to Your Pre-Chat Form in Messaging for In-App and Web
  The UI SDK automatically displays dropdown fields that are set up in Salesforce. The Core SDK provides a new ChoiceList pre-chat field type.
• Choose When to Show a Pre-Chat Form in Messaging for In-App and Web
• Fine-Tune Messaging Session Expiration to Accommodate Your Security Requirements
• Use Branding Tokens and String Tokens for the Latest Features
  See Customize Colors and Customize Strings.

API Changes

• Added APIs for conversation list support. See Conversation Lists.
  • CoreClient.conversations()
  • CoreClient.conversationsPaged()
• Added API for bot options menu.
  • Participant.clientMenu
  • ParticipantClientMenu
• Added API for exposing the currently configured business hours. See Business Hours.
  • CoreClient.retrieveBusinessHours()
  • BusinessHoursInfo
• Added pre-chat fields for dropdown fields.
  • ChoiceList
  • ChoiceListField
  • ChoiceListValue
  • ChoiceListValueDependency
• New branding tokens. See Customize Colors.
  • Client menu tokens: smi_participant_client_menu_background, smi_participant_client_menu_item_text, smi_participant_client_menu_item_background, smi_participant_client_menu_item_icon, smi_participant_client_menu_search_icon, smi_participant_client_menu_item_focus_background
  • List picker token: smi_list_picker_title_background
• New string tokens. See Customize Strings.
  • Client menu tokens: smi_participant_client_menu_title, participant_client_menu_title_accessibility
  • Business hour tokens: smi_business_hours_outside, smi_business_hours_outside_accessibility
  • Mid-conversation pre-chat tokens: smi_chat_start_conversation, smi_chat_start_conversation_feed_input_text_accessibility, smi_delivery_status_error_additional_information_required
  • Share view tokens: smi_header_share_gif_viewer, smi_header_share_pdf_viewer
  • Other tokens: smi_pre_chat_choice_list_none, smi_misc_unknown
• Minimum SDK version changed to API Level 23 (Android 6, Marshmallow) from API Level 21.

Bug Fixes

• Fixed an issue where the network banner didn’t show up when entering a conversation without a network connection.
• Fixed issue with unused branding tokens (smi_loading_screen_avatar, smi_loading_screen_background, smi_loading_screen_input_text_placeholder). Overriding these tokens should now update their respective UI elements correctly.
• Fixed a margin issue in the loading view next to the text input.
• Fixed an issue when reentering a conversation where the local user's messages showed up as a remote user's messages.
• Fixed an UnsatisfiedLinkError by upgrading the minimum SDK version to API Level 23 (Android 6, Marshmallow) from API Level 21.

Known Issues

• 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”.