feat: expo push notifications #86
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
D4ryl00
force-pushed
the
feat/expo-push-notif
branch
from
5be77da
to
f414eeb
Compare
D4ryl00
force-pushed
the
feat/expo-push-notif
branch
3 times, most recently
from
d6e4944
to
7449966
Compare
…ribe to Signed-off-by: D4ryl00 <d4ryl00@gmail.com>
… on PostReply transactions Signed-off-by: D4ryl00 <d4ryl00@gmail.com>
…Token and register device to the new push notification service Signed-off-by: D4ryl00 <d4ryl00@gmail.com>
D4ryl00
force-pushed
the
feat/expo-push-notif
branch
from
405143f
to
17e071a
Compare
Signed-off-by: D4ryl00 <d4ryl00@gmail.com>
jefft0
approved these changes
Jul 1, 2024
|
🎉 This PR is included in version 1.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the first iteration of Expo push notifications in dSocial.
This enables push notifications for PostReply transactions, so when you reply to a user post.
This PR creates a new notification service that monitors the PostReply transaction on the indexer service, and sends push notifications to users registered on it.
The registration on the notification service is made on the onboarding. But you can also force-register a user in the profile tab.
The discussion that helped me to understand why the notification server got an error on the opened stream with the indexer service: connectrpc/connect-go#757
To build the project, we should have now google-services.json
andGoogleService-Info.plistin themobilefolder, and donpx expo prebuild --clean` at least one time.fixes #87