[Enhancement] Push notification token registration is stubbed with three TODOs and never reaches a backend

[RUKAYAT-CODER]

Overview

src/services/pushNotifications.ts carries three TODO markers — at lines 205, 209 and 350 — all reading variations of "Replace with actual API call when backend is ready". registerTokenWithBackend() therefore does not register anything, so no device can receive a push even though app.json configures expo-notifications, declares UIBackgroundModes: ["remote-notification"], and requests RECEIVE_BOOT_COMPLETED. src/components/mobile/NotificationSettings.tsx:72 has a matching // TODO: Sync with backend, so notification preferences are local-only. The whole notification surface — prompt, permission sheet, settings, store, channel setup — is built around a transport that does not exist.

Specifications

Features:

• Real token registration and de-registration endpoints wired up
• Notification preferences synchronised with the backend
• Token refresh handled when Expo rotates the push token
• Registration failures surfaced rather than silently swallowed

Tasks:

• Define the token-registration contract with the backend team and record it in docs/NOTIFICATION_STRATEGY.md
• Implement registerTokenWithBackend() and the corresponding unregister call on logout
• Wire NotificationSettings.tsx preference changes to the API
• Handle token rotation via the Expo push-token listener
• Extend tests/pushNotifications.test.ts and src/__tests__/services/pushNotifications.test.ts to cover registration, rotation and failure

Impacted Files:

• src/services/pushNotifications.ts
• src/components/mobile/NotificationSettings.tsx
• src/services/pushChannelSetup.ts
• docs/NOTIFICATION_STRATEGY.md

Acceptance Criteria

• A device receives a push notification end to end
• Preferences persist across reinstalls via the backend
• Token rotation re-registers automatically
• Registration failures are visible in Sentry

[bobo-24]

Hi! I’m a full-stack developer with a strong blockchain background, and I’m confident I can resolve this issue quickly and effectively. I’ll deliver a clean, reliable solution with immediate attention to detail, ensuring it’s completed as soon as possible. Please assign it to me—I’m ready to get started right away.

[OkonkwoEmeka]

@OkonkwoEmeka has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hi maintainer, please i’d love to work on this issue. i’m a professional developer with experience in this area, and i’m confident i can handle it properly and finish it on time.

i’ve reviewed the issue and understand the expected outcome. i’ll follow the existing codebase patterns, keep the implementation focused, test the relevant behavior, and make sure the final pr meets the project’s requirements.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OkonkwoEmeka to this issue.

[MaxiTech444]

@MaxiTech444 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Can I work on this please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MaxiTech444 to this issue.

[sadeeq6400]

@sadeeq6400 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Good day

I have read the requirements of this issue and i am confident that i can solve this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @sadeeq6400 to this issue.

[lamborghini21]

@lamborghini21 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello boss, I'd love to work on this issue and I promise to deliver results in 24 hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @lamborghini21 to this issue.

[drips-wave]

Congratulations, @sadeeq6400! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @sadeeq6400: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@sadeeq6400's PR #1066 was approved and merged by @RUKAYAT-CODER.

🏆 @sadeeq6400: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,308 total points). Track your full progress on GrantFox.

👏 Great work, @sadeeq6400! Keep contributing to rinafcode.

[drips-wave]

This issue has been completed by @sadeeq6400 as part of the Stellar Wave Program's 8th Wave 🥳

😎 @sadeeq6400: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.