What's new in the Notification SDK

This section provides an overview of changes introduced in the Notification SDK to facilitate the integration of the SDK and provide information on backward compatibility.

Version 4.32.0

.NET

The Notification SDK Server has been re-factored to modernize and improve the code resulting in the following changes. We recommend that you review your integrations to make sure these changes are reflected in your code.

General changes

Previous versions

Version 4.31.0

.NET

Migrated from .NET Framework to .NET 6

The SDK has been migrated from .NET Framework to .NET 6 to leverage upgraded features.

iOS

Bitcode support has been eliminated

Following the deprecation of Bitcode by Apple, we no longer support and have removed all Bitcode from the SDK framework.

Version 4.30.1

.NET and Java

Create notifications based on server-set priority

It is now possible to create the notification based on a priority set by the server. With this, it is for instance possible that while the device is in a sleep mode, a high priority notification is received without a delay and wakes up the screen.

Android

Target API increased to 33

To meet new requirements for apps published on the Google Play Store, the target version of the SDK has been increased to Android 13 with API level 33. This change is needed to avoid APK rejection caused by security issues found in older API versions.

New permission required

Android 13 (API level 33) and later supports a runtime permission for sending non-exempt (including Foreground Services (FGS)) notifications from an app: POST_NOTIFICATIONS. This change helps users focus on the notifications that are most important to them.

For more information, refer to the Android developer documentation on how to check if your app can send notifications.

iOS

Full control over notification body and title

The SDK now offers full control over the notification body and title. This can facilitate automation and potential integration of the Notification SDK Client with third party solutions used in combination with the Notification SDK.

Version 4.30.0

Android

Target API increased to Android 12 (API 31)

To meet new requirements for apps published on the Google Play Store, the target version of the SDK has been increased to Android 12 with API 31 or higher. This change is needed to avoid APK rejection caused by security issues found with the older API versions.

Minimum supported version increased to Android 6 (API 23)

The minimum supported version has been increased to fully support new features and devices. Deprecated code has been replaced and simplified to be compatible with API 23 or higher.

iOS

Increased the minimum supported version to iOS 13

The minimum supported version has been increased to fully support all ARM64 devices and SwiftUI features. Deprecated code has been removed and replaced with code fully supporting iOS 13 or higher.

Fixed internal error conversion issues

Error codes converted between Objective-C and Swift need to have the NSCustomError setting implemented to display the correct value. Without this setting, the wrong codes could be displayed from the enum. The setting has been implemented in all the remaining error handling objects.

Version 4.29.2

iOS

Change of framework name to MSSNotificationClient

The framework name has been changed from NotificationClientSDK to MSSNotificationClient. To use the new Objective-C API, replace all previous NotificationClientSDK imports with #import <MSSNotificationClient/MSSNotificationClient.h>.

API updates – NSErrors API support for Objective-C added

The Objective-C API points no longer throw an NSException. All API points that previously would throw such an NSException now require an NSError pointer. If an error occurs, it will be attached to the pointer that is provided as a parameter. Refer to the Objective-C sample included in the product package for full code examples.