Skip to content

September 2017 Release 2
Compare
Choose a tag to compare
@sfyz sfyz released this 15 Sep 14:09
208.4.0
814ff9d

Service Cloud Snap-ins for Android Release Notes

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

  • Knowledge version 2.1.1
  • Case Management version 2.0.0
  • Live Agent Chat version 1.1.1
  • SOS version 2.2.0

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

Summary

Patch release that fixes a bug related to Live Agent Chat file transfer.

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

Fixes

  • Live Agent Chat: Fixed a crash that occurred during file transfer when selecting photos from certain applications, such as Samsung's Gallery app.

Known Issues

  • Knowledge and Case Management: The app crashes if it receives any GCM push notification and you haven’t initialized the Salesforce Mobile SDK (using SmartStoreSDKManager.initNative). Workaround: Explicitly initialize the Salesforce Mobile SDK in your app’s initialization code.
  • Case Management: Read-only fields in Case Action layouts display as editable fields when creating a new case using the SDK’s Case Publisher. Workaround: Ensure that there are no read-only fields in the Case Action layout you use to create cases with the SDK.
  • Live Agent Chat: If the user exits the app during a full screen chat session and then the agent ends the session, the app crashes when it's relaunched if the OS has to reload the app into memory.
  • Live Agent Chat: If the user loses the connection during a chat session, their message appears to get sent to the agent even when there's a network failure. Workaround: Detect connectivity issues explicitly and prompt user when they occur.
  • SOS crashes when the app uses SosConfigurationBuilder.builder().connectingUi(false) and the session ends before the agent connects. This affects all versions of SOS.
  • SOS: If agent availability returns a status of Unknown, it means that we're not able to determine if an agent is available before attempting a session. Typically, SOS can still function normally in this case; we recommend that you allow customers to attempt SOS sessions even with an Unknown status. This status could be due to a network failure or that the pod server URL has changed. Check your org setup to see if the pod URL has changed. If it has, then update your app accordingly.
  • SOS: Android's TalkBack accessibility feature is not supported during screen sharing.
Assets 2
Loading