For react native users who are using SFMC, the setup is similar to the iOS manual setup.
For react native users who are initializing in native code, they can opt to either implement the automatic or manual setup
For react native users initializing in react native, they can call Radar.nativeSetup() in the app delegate to use the automatic setup. React native users who are using a library to implement UNUserNotificationCenterDelegate (e.g. expoNotifications) are only able to use the automatic setup (unless they wish to create and use a modified fork of that notification library)
Dogfooded this current build, refer to the values that I generated on the last day (sept 6)
I also think we might want to start sending up notification authorization in config and track just like we do for location authorization. The server work to handle can follow.
Changes to the interface and developer experience:
UNUserNotificationCenterDelegate
Radar.nativeSetup()
in the app delegate to use the automatic setup. React native users who are using a library to implementUNUserNotificationCenterDelegate
(e.g. expoNotifications) are only able to use the automatic setup (unless they wish to create and use a modified fork of that notification library)Dogfooded this current build, refer to the values that I generated on the last day (sept 6)
https://expo.dev/accounts/radarlabs/projects/waypoint/builds/079839d6-e7ca-4e2c-8351-04d18e15b721 (this is a "bricked" waypoint build which only can do trackonces using this build)
Additional QA:
working with one signal
Braze:
SFMC
associated server PRs:
feature flags: https://github.com/radarlabs/server/pull/6106 proper parsing of the metadata string into a json: https://github.com/radarlabs/server/pull/6136