Closed mattmikolay closed 1 month ago
Latest commit: 24eccfb249fd416cdb9782dba750fb58ac38c4d6
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
javascript-nextjs-example | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 15, 2024 9:49pm |
javascript-slack-connect-example | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 15, 2024 9:49pm |
javascript-slack-kit-example | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 15, 2024 9:49pm |
Now that #243 moved
KnockExpoPushNotificationProvider
to the new@knocklabs/expo
package, we need to provide a way for non-Expo React Native applications to register push tokens to a channel for the current user.This PR adds a new context provider
KnockPushNotificationProvider
to@knocklabs/react-native
. This context provider exposes two functions,registerPushTokenToChannel
andunregisterPushTokenFromChannel
. These can be used to manually register/unregister push tokens retrieved from a provider such as Firebase Cloud Messaging.Additionally,
KnockExpoPushNotificationProvider
has been refactored to use this newKnockPushNotificationProvider
.I tested these changes on an Android device and confirmed push notifications can still be received using the Expo sample app.