MSSSecureMessagingClient.h is the SDK's umbrella header and should be used for all integrations. Using 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
#import <MSSSecureMessagingClient/SecureMessagingSDKClient.h>to
#import <MSSSecureMessagingClient/MSSSecureMessagingClient.h>A deprecation notice for
SecureMessagingSDKClient.hwill be added in an upcoming release, and it will be removed from public headers in a future version of the SDK.
Android
To use the Secure Messaging SDK Client in your Android project
Link SecureMessagingSDKClient.aar from the OneSpan Mobile Security Suite package to your project's classpath.
iOS
To use the Secure Messaging SDK Client in your iOS project
Link MSSSecureMessagingClient.xcframework from the OneSpan Mobile Security Suite package to your Xcode project.
For Objective-C projects, use the .mm file extension when integrating the SDK. This is required as the SDK uses Objective-C++ and .m files are not supported.
Your project must be compiled with the libc++ standard library.
You are now ready to use the Secure Messaging SDK Client.
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!