Skip to content

June 2018 Release 2 (Patch Release)
Compare
Choose a tag to compare
@sfyz sfyz released this 21 Jun 18:30
214.0.1
f019a0b
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 patch release (214.0.1) applies to the following component versions:

  • Knowledge version 4.1.0
  • Case Management version 4.1.0
  • Live Agent Chat version 3.1.0
  • SOS version 4.0.2
  • Common version 6.1.0

For more info about the SDK, see the Snap-Ins SDK Product Page. Check out the version release history to learn about past versions of the SDK.

Summary

Patch release that fixes a potential crash during an SOS session.

See the June 2018 Major Release for general details about the SDK.

Fixes

  • SOS: Fixed a logging-related crash that may occur when starting an SOS session.

Known Issues

  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Live Agent Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • 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.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.
Assets 2
Loading