laravel-expo-notifier
laravel-expo-notifier copied to clipboard
YieldStudio
Easily manage Expo notifications with Laravel. Support batched notifications.
After upgrading to 0.0.14 I'm now getting this error: YieldStudio\LaravelExpoNotifier\Exceptions\ExpoNotificationsException: Expo service error: HTTP `400` response: {"errors":[{"code":"VALIDATION_ERROR","message":"\"useFcmV1\" must be a boolean.","isTransient":false,"requestId":"6471d747-14dc-4caf-a9e1-0388 This is what my expo-notifications.php config looks like: `'use_fcm_legacy_api'...
I want to store each notification in database with user id so I can send all this user notification to the user
```` while ($ticketStorage->count() > 0) { $tickets = $ticketStorage->retrieve(); $ticketIds = $tickets->pluck('id')->toArray(); $response = $expoNotificationsService->receipts($ticketIds); if ($response->isEmpty()) { break; } $this->check($ticketStorage, $tickets, $response); } ```` When ->receipts() has an error,...
Expo is limited to [600 notifications per seconds](https://docs.expo.dev/push-notifications/sending-notifications/#request-errors).
Add ability to run on multiple server by implementing a row locking system. Currently running on multiple servers can cause duplicate notifications.
It would be nice to implement a retry ([exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff)) system for failed batched notifications. For non-batched notifications, it would be necessary to throw an exception or dispatch an event...
- [ ] Delayed notifications - [ ] Service - [ ] Urgent notifications - [ ] Storage - [ ] Push tickets/receipts processing
- [ ] Deploy Docusaurus - [ ] Custom storage documentation - [ ] Complete the existing documentation - [ ] Add some Expo references to explain concepts
Metadata
Owner
Metadata
Easily manage Expo notifications with Laravel. Support batched notifications.