--- title: "Release Notes Version 4.35.0" slug: "sec-msg-sdk-client-release-notes-4-35-0" updated: 2026-11-03T14:27:18Z published: 2026-11-03T14:27:18Z canonical: "docs.onespan.com/sec-msg-sdk-client-release-notes-4-35-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Release Notes Version 4.35.0 ## Deprecations #### SecureMessagingSDKClient.h header deprecated The `SecureMessagingSDKClient.h` header is declared as deprecated and will be removed from public headers in a future version of the SDK. Internal changes in a previous SDK version to the C++ header `SecureMessagingSDKClient.h` may cause build errors when the header is imported directly. `SecureMessagingSDKClient.h` is not intended for public use, it is an internal C++ header, not the SDK's umbrella header. If your project imports this header directly, update your import statement as follows: Change from ```cpp #import ``` to ```cpp #import ``` `MSSSecureMessagingClient.h` is the SDK's umbrella header and should be used for all integrations going forward. ## New features and enhancements ### All platforms #### Support for UTF-8 BMP encoding The SDK now supports UTF-8 encoding of characters in the Unicode Basic Multilingual Plane (BMP) with a UTF-8 BMP font table (`FORMATTED_TEXT_FONT_TABLE_INDEX_UTF8_BMP`) in formatted text messages. Previously, formatted text fields were limited to a fixed set of character encodings (ISO Latin, Katakana, Greek, Turkish, etc.), each mapped to a specific font table index. With this version, a new font table index is available, allowing formatted text fields to carry any character from the Unicode Basic Multilingual Plane (accented Latin, €, Cyrillic, CJK etc.) in transaction, challenge, and free-text messages. When a message is received that uses UTF-8 BMP encoding, the SDK now decodes it correctly and surfaces the text through the existing `FormattedText` APIs. The SDK now validates the encoding type in the message header. If a message specifies an encoding type other than the legacy encoding or UTF-8 BMP, the SDK now returns `unsupportedMessageEncoding` (-`4868`). For more information, see [Integrate the Secure Messaging SDK Font Tables](/mobile/docs/sec-msg-sdk-client-ig-integrate-sdk-font-tables-4-35-0). ### Android #### Maven-based integration The SDK artifact is now delivered as a local Maven repository, in addition to the previously published standalone aar artifact, and the package now also includes a documentation jar file. For more information, see [Maven-based integration](/mobile/docs/sec-msg-sdk-client-ig-integrate-the-sdk-4-35-0#mavenbased-integration1). ### iOS #### Enhanced error lookup The technical documentation included in the product package now includes the numeric value of each error code (`SecureMessagingSDKErrorCodesObjC`), making error lookup easier. #### Prepare sample application for iOS 27 The sample application has been updated to adopt the UIKit scene-based application lifecycle which is required for apps to be built with iOS 27 and later. For more information, refer to the [iOS documentation](https://developer.apple.com/documentation/UIKit/transitioning-to-the-uikit-scene-based-life-cycle) and [iOS & iPadOS 27 Release Notes](https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-27-release-notes). ## Other notices ### iOS #### Stricter linker requirements With iOS SDK 16.0, Apple introduced stricter linker requirements for explicit dependencies. As a result, the project may show C++ linker errors. If you encounter these errors, link the standard C++ library as described in the [Integration Guide](/mobile/docs/sec-msg-sdk-client-ig-integrate-the-sdk-4-35-0#ios). ## Supported platforms For information on the supported operating systems and platforms supported by Mobile Security Suite and the affiliated SDKs, see [Supported platforms.](/mobile/docs/mss-rn-supported-platforms-4-40-0) ## Known issues For information on issues that have not yet been resolved in this release of Mobile Security Suite, see [Known issues](/mobile/docs/mss-rn-known-issues-4-40-0). ## API reference documentation and sample applications To learn more about the public APIs and their functions, exceptions, and error codes, refer to the technical documentation that is included in the product package for each SDK and each platform. In the product package, you can also find the sample applications provided for each platform to see examples of how the SDKs can be used. > These sample apps are intended only to demonstrate basic scenarios and SDK usage. They are not designed to be copied directly into production projects! ## 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](/mobile/docs/mss-rn-third-party-licenses-4-40-0).