DRAFT: Add initial implementation for iOS push notifications using APNs #1095
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.
Pull Request Description
This is a draft PR which adds the ability to handle apple push notification service (APNs).
To do this, I'm using a package
push
which handles platform specific implementations for iOS and Android. For iOS, it uses APNs (apple push notification service). For Android, it uses FCM (Firebase Cloud Messaging). I'm only implementing the iOS platform specific implementation here. Ideally, we can ignore the Android specific portions, and use UnifiedPush for Android devices. Whether or not this is possible is up in the air as we would have multiple packages handling push notifications on Android (may clash with each other).Additionally, implementing push notifications requires a separate server in order to perform notification polling and sending out push notifications for devices. I've set up a simple server to handle this for now, and the domain is https://thunderapp.dev.
There is still a lot of work required for this to function properly. I'll add a to-do list here:
While I'm developing the server code, I'll keep it closed-source. I'll most likely make it open-source once I'm done with all the local testing (to ensure that no keys are accidentally committed to the repository)
Another note: I've shifted the notification logic and moved it from 'main
into
ThunderApp`. I hope this still works with the local notification logic!Issue Being Fixed
Issue Number: #219
Screenshots / Recordings
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-01-29.at.10.59.01.mp4
Checklist
semanticLabel
s where applicable for accessibility?