Skip to content

April 2024 Patch Release

Latest
Latest
Compare
Choose a tag to compare
@colinmacdonald colinmacdonald released this 29 Apr 17:19
· 2 commits to master since this release
224.2.7
5065c67
This commit was signed with the committer’s verified signature.
colinmacdonald Colin MacDonald
GPG key ID: 09A8BB1366586B9E
Learn about vigilant mode.

Release Notes: Embedded Service SDK for Android

Note: These release notes describe the Embedded Service Chat SDK. If you're not already using Chat, check out Messaging for In-App, a newer in-app chat solution: Messaging for In-App Developer Guide.

This patch release (SDK version 224.2.7) includes the following components:

  • Chat version 4.3.6
  • ServiceCommon version 8.0.6

To install the SDK, follow these installation instructions. For additional info about the SDK, check out the Service SDK Developer Center. Refer to the version release history to learn about past versions of the SDK.

Running into an issue? Create a case.

New Features

Bug Fixes

  • Removed the Knowledge and Cases SDKs from the Service SDK. This resolves an issue with out of date and unsupported dependency versions contained in them. These two SDKs have not been supported since the Winter 23 release. Please see this document for more info: https://help.salesforce.com/s/articleView?id=000391938&type=1.
  • Using com.salesforce.service:servicesdk:<latest> is now equivalent to using com.salesforce.service:chat-ui:<latest> due to the Service SDK only containing the Chat UI SDK going forward.

Known Issues

  • If you set defaultToMinimized to false then when a user gets transferred to another agent, the chat feed becomes hidden behind the chat queue and you can't speak with the agent. Workaround: Set defaultToMinimized to true, which is also the default value for this setting: chatUIConfigurationBuilder.defaultToMinimized(true)
  • If you use an incorrect button ID in your chat configuration, the chat will fail and your SessionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • Case creation using the ChatEntity class does not work for Omni-Channel routing without a setup change to your org. Workaround: Raise a ticket with Salesforce.com to ensure that Omni-Channel is enabled to create a Case in your org. Note that Contact creation works fine with Omni-Channel, and Live Agent routing works correctly for both Cases and Contacts.
Assets 2