New features and enhancements
All platforms
Support for UTF-8 BMP encoding
The server SDK now supports UTF-8 encoding of characters in the Unicode Basic Multilingual Plane (BMP) in transaction, challenge, and free-text messages. Servers can now produce messages using the new FORMATTED_TEXT_FONT_TABLE_INDEX_UTF8_BMP (5) font table index, and the SDK uses it to encode the message body as raw UTF-8 bytes and set the encoding type field in the message header accordingly. This then signals the client SDK that the content uses UTF-8 BMP rather than the legacy 16-bit 3-character encoding. To control which characters are permitted in UTF-8 BMP–encoded fields, servers can call setUtf8BmpAllowedCharacters, passing a string whose individual characters form the allowlist. The default is null, and when this is passed all valid BMP characters are accepted. Any character that violates the allowlist, or that is a surrogate or forbidden control character, causes the SDK to throw a SecureMessagingSDKException with FONT_TABLE_UNSUPPORTED_CHARACTER.
Only use UTF-8 BMP encoding when all clients that receive these messages use Secure Messaging SDK Client 4.35.0 or later. Earlier client versions do not support UTF-8 BMP, they decode this type of message with the legacy encoding, so the text is displayed incorrectly or the message is rejected.
For more information, see Integrate the Secure Messaging SDK Server Font Tables.
Supported platforms
For information on the supported operating systems and platforms supported by Mobile Security Suite and the affiliated SDKs, see Supported platforms.
Known issues
For information on issues that have not yet been resolved in this release of Mobile Security Suite, see Known issues.
Third party licenses
For information on third party dependencies associated with Mobile Security Suite and the affiliated SDKs in this release, see Third party licenses.