-
Notifications
You must be signed in to change notification settings - Fork 21
Migration guides
- Changes in documentation
- Migration guide (from 12.15.x to 12.16.x)
- Migration guide (from 11.x to 12.x)
- Migration guide (from 10.x to 11.x)
- Migration guide (from 9.x to 10.x)
- Migration guide (from 8.x to 9.x)
- Migration guide (from 4.x to 5.x)
Basic In-App notifications
renamed to Mirror Push notifications, Full featured in-app notifications
renamed to In-App messages.
In version 12.16.0
of the SDK, the following API change was made to the willPresentInForeground
method of the MMMessageHandlingDelegate
protocol:
- @objc optional func willPresentInForeground(message: MM_MTMessage?, notification: UNNotification, withCompletionHandler completionHandler: @escaping (MMUserNotificationType) -> Void)
+ @objc optional func willPresentInForeground(message: MM_MTMessage?, notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -> Void)
This change allows the use of the UNNotificationPresentationOptions.list
option introduced in iOS 14. For a detailed implementation example check How to display messages when app is running in the foreground?
If you were using previous versions of WebRTCUI, you need to replace your setup with the new WebRTC Configuration and check the new identity modes for enabling calls. Please check the dedicated WebRTC migration guide for more details.
In-App messages feature is supported since 11.0.0 version. This feature is disabled by default, in order to enable it check how to enable In-App messages.
At version 10.0.0 minimum deployment target changed to iOS 12.
If you have any questions or suggestions, feel free to send an email to support@infobip.com or create an issue.
- Library events
- Server errors
- Users and installations
- Messages and notifications management
- Inbox
- Geofencing service
- Privacy settings
- In-app chat
- WebRTC Calls and UI