Skip to content

April 2021 Patch Release
Compare
Choose a tag to compare
@sfyz sfyz released this 07 Apr 17:54
· 16 commits to master since this release
224.0.3
88a7563
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.

Release Notes: Embedded Service SDK for iOS

This release (SDK version 224.0.3) includes the following components:

  • Chat version 4.0.7
  • Knowledge version 3.5.6
  • Case Management version 2.2.6
  • SOS version 3.11.6
  • ServiceCore version 4.2.6

To download 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.

⚠️ When building an app with the Service SDK on an M1-based Mac, the Xcode iOS simulator doesn't currently work. Workaround: Either test your app on real iOS devices, or use an Intel-based Mac until we can provide an update.

Summary

This release requires Xcode 12 and uses a minimum version of iOS 12. This release also contains bug fixes.

Fixes

  • Chat: Fixed an issue where the chatbot quick reply buttons were not respecting accessibility changes.
  • Chat: Fixed an issue where the chatbot window menus were not aligned properly for long text strings.
  • Chat: Fixed an issue where the chatbot was not handling no agents available during an agent transfer.
  • Chat: Fixed an issue where the quick reply buttons were not displaying properly for long text strings.
  • Chat: Changed the color of the agent typing animation dots to be more accessible.
  • Chat: Fixed an accessibility issue where the required field value was not being read out loud.
  • Chat: Fixed a windowing issue when the user tried to start a session while picture-in-picture is active.
  • Chat: Updated the insets on the quick reply chat buttons.

Component Updates

  • SOS: Updated to OpenTok release 2.18.1.

Known Issues

  • When building an app with the Service SDK on an M1-based Mac, the Xcode iOS simulator doesn't currently work. Workaround: Either test your app on real iOS devices, or use an Intel-based Mac until we can provide an update.
  • Adding a plist value in your app for View controller-based status bar appearance and setting it to YES will have no effect in the SDK and in your app. If you set this value to NO, you can then set Status bar style and Status bar is initially hidden in the plist file to control the status bar in the app.
  • Chat: When dragging a finger over UI elements while using VoiceOver, some elements in the chat feed are not read aloud.
  • Chat: Case creation using the SCSPrechatEntity 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.
  • 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.
  • SOS: If agent availability returns an SOSAgentAvailabilityError (3003), there was an error while calling the agent availability REST API. This could mean that your SOS credentials are incorrect. Verify that your credentials are correct. This error can also 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, update your app accordingly. In some of these situations, SOS can still function normally even when receiving this error, so we recommend that you allow a customer to attempt an SOS session even with this error.
Assets 2
Loading