feat: add Expo Push notifications for mobile and configure EXPO_ACCESS_TOKEN #30
Owner
- Backend: add expo_push_tokens table, expo-register/unregister endpoints, hybrid VAPID+Expo push sender
- Mobile: register Expo push token on app launch, bell toggle on medicine/pharmacy detail screens
- .env.example: document EXPO_ACCESS_TOKEN configuration
- Dark mode hover fixes for search suggestions and recent buttons
- Backend: add expo_push_tokens table, expo-register/unregister endpoints, hybrid VAPID+Expo push sender
- Mobile: register Expo push token on app launch, bell toggle on medicine/pharmacy detail screens
- .env.example: document EXPO_ACCESS_TOKEN configuration
- Dark mode hover fixes for search suggestions and recent buttons
Ichitux
added 1 commit 2026-07-13 10:22:32 +00:00
Run Tests on Branches / Detect Changes (push) Successful in 13s
Details
Run Tests on Branches / Backend Tests (push) Successful in 1m58s
Details
Run Tests on Branches / Frontend Tests (push) Successful in 1m53s
Details
Run Tests on Branches / Frontend Mobile Tests (push) Successful in 1m49s
Details
Merge pull request 'feat: add Expo Push notifications for mobile and configure EXPO_ACCESS_TOKEN' (#30) from feat/expo-push-notifications into main
Reference in New Issue
Block a user
Delete Branch "feat/expo-push-notifications"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?