Skip to content

December 2017 Release
Compare
Choose a tag to compare
@sfyz sfyz released this 14 Dec 20:08
210.1.0
c660120
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Service Cloud Snap-Ins for Android Release Notes

This release (210.1.0) applies to the following component versions:

  • Knowledge version 3.0.0
  • Case Management version 3.0.0
  • Live Agent Chat version 2.0.1
  • SOS version 3.1.0

For more info about the SDK, see the Snap-Ins SDK Product Page.

See the version release history to learn about past versions of the SDK.

Summary

Patch release that addresses a few Chat and SOS bugs.

See the October 2017 release for general details about the SDK.

Fixes

  • Live Agent Chat: Fixed problem where agent availability would not return a result in the event of a Live Agent server switch.
  • Live Agent Chat: Fixed a problem with missing translations for strings present in chat-ui. Previously, only English text existed for the following strings:
    • chat_dialog_select_image_source_choose
    • chat_session_ended_by_agent
    • chat_feed_content_description
    • chat_file_transfer_requested
    • chat_file_transfer_canceled
    • chat_file_transfer_failed
    • chat_image_selection_failed
    • chat_permission_not_granted
    • pre_chat_toolbar_title
    • pre_chat_button_start
    • pre_chat_field_list_description
    • pre_chat_banner_text
    • salesforce_message_input_hint
  • SOS: Minor adjustment to the SOS session timeout value to reduce the possibility of a dropped call.

Known Issues

  • KitKat (Android 4.4) devices crash when using the Snap-ins SDK and Google Play Services Security Provider. Workaround: Avoid invoking ProviderInstall on KitKat devices by checking the current build version in your code.
  • Live Agent Chat: Case creation via pre-chat entity mapping does not work when using Omni-Channel routing. Contact creation still works correctly. Workaround: Use Live Agent routing instead, or avoid creating cases with pre-chat fields. Note that Live Agent routing is currently only available in Salesforce Classic.
  • Knowledge: When caching content for offline use, the log may show "Error inserting using {redacted sql} into {TableName}". There is no impact on the application behavior beyond this log statement.
Assets 2
Loading