Latest iOS Messaging SDK version - 3.3.0
This is the latest version of the iOS Messaging SDK release notes. To view all release notes for previous versions, please click here.
iOS Mobile App SDK v3.3 contains support for the Post Conversation Survey feature, support for iOS 12, XCode 10 and Swift 4.2 and addresses several bugs reported by customers.
iOS Mobile App SDK v3.3 is compatible with XCode 10, Swift 4.2 and iOS versions 9 through 12.
Post Conversation Survey
Available to all customers? No. Please contact account team.
The post conversation survey enables brands to both collect feedback and measure their success from their consumers after conversations have taken place. The survey is delivered via a conversational experience to drive higher completion rates and provide consumers with the best experience possible.
Brands can customize the survey to their needs, including predefined questions (CSAT, NPS and FCR), custom questions and free text, as well as the ability to configure the logic and flow from question to question.
This enables brands to prove the success of messaging and compare their KPIs across different channels. Additional information about Post Conversation Survey can be found here .
Support for iOS 12, XCode 10 & Swift 4.2
Available to all customers? Yes.
Mobile App SDK v3.3 supports iOS 12, XCode 10 & Swift 4.2.
In some cases, when consumers would go into the conversation screen, the loading progress bar would get stuck.
When starting to fill a secure form, if a customer exits out of the form and opens a new secure form, the values from the first form appear in the new form for about a second and then disappear.
When applying a regex for real time masking, the entire string will be affected rather than only the matching part.
Missing auto scroll to bottom when a conversation is closed.
The first message is hidden when using the Control History APIs. After sending the second message, all messages will be visible.
In some cases, when consumers send the app to the background and later return to the conversation screen, the socket will not get connected and the consumer will not be able to send/receive messages.
When going into the conversation screen after the app was killed, the screen will be scrolled to the top instead of to the bottom.
When replacing rootViewController, in-app push notifications stops working.
If a failure occurred while unregistering for Push Notifications, customers were unable to logout from the SDK.
When Voiceover is turned on, the Secure Forms ‘X’ button reads “stop” instead of “close”.
When Voiceover is turned on and the send button is customized, the send message button reads as “button” instead of the button’s functionality.
When Voiceover is turned on, when reading messages, agent reads as “agent” instead of the agent’s nickname.
- Resolving unauthenticated conversations fails when setting the flag ‘show history for closed messaging conversations’ to no. The feature works as expected when the flag is set to yes.