You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The update closure will now be triggered by both "Push Opened" and "Push Received" events by default. Previously, it would only be triggered by "Push Opened" events.
To continue subscribing only to "Push Opened" events, pass in [.opened] for the parameter payloadTypes. Alternatively, implement your update closure to check that the type from the Braze.Notifications.Payload is .opened.
When receiving a push notification with content-available: true, the Braze.Notifications.Payload.type will now be .received instead of .opened.
Marks the following deprecated APIs as unavailable:
Removes the deprecated BrazeLocation class in favor of BrazeLocationProvider.
Fixed
Fixes a crash when handling a scheme-based deep link containing a registered applink domain (e.g. applinks:example.com with a deep link to app://example.com/path).
The following notifications will trigger this subscription:
Notifications received in the foreground
Notifications with the field content-available: true received in the foreground or background
The following notifications will not trigger this subscription:
Notifications received while terminated
Notifications received in the background without the field content-available: true
The new parameter payloadTypes will allow you to subscribe to "Push Opened" events, "Push Received" events, or both. If the parameter is omitted, it will subscribe to both by default.
If you are using manual push integration, you will need to first implement UNUserNotificationCenter.userNotificationCenter(_:willPresent:withCompletionHandler:), and make sure to call Braze.Notifications.handleForegroundNotification(notification:) within your implementation. Then, use subscribeToUpdates as noted above. See our guide on push notification integration for more info.