laravel-notification-channels/expo

Added

• ExpoGateway::getReceipts

Backwards-compatible release adding deferred-receipt fetching and ticket-ID surfacing so consumers can persist ticket IDs and poll /push/getReceipts later.

• ExpoResponse::ok() now optionally carries the array of ticket IDs accepted by Expo; ExpoResponse::tickets() returns them (empty array on failed/fatal).
• ExpoGateway interface gains getReceipts(array $ticketIds): array. ExpoGatewayUsingGuzzle implements it against https://exp.host/--/api/v2/push/getReceipts.
• New NotificationChannels\Expo\Exceptions\CouldNotGetReceipts exception thrown on non-200 responses from the receipts endpoint. Separate from CouldNotSendNotification so consumers can distinguish "send failed" from "receipt poll failed."
• New NotificationChannels\Expo\Events\ExpoNotificationSent event dispatched on the success path, carrying (notifiable, notification, tickets) where tickets is a token-string → ticket-UUID map. App-specific metadata travels on the notification instance — consumers read it via $event->notification->yourField in their listeners.

No breaking changes — existing callers that don't listen for ExpoNotificationSent or call getReceipts() see identical behaviour.

Complete revamp of the channel with much thanks to @mabdullahsari

• Requires PHP 8.3 and Laravel 11
• Fully featured Expo Message with more options
• Includes casting for Expo notification tokens
• Includes validation for Expo notification tokens
• Fires NotificationFailed events to handle invalid tokens

• Channel revamp

What's Changed

• Add support for subtitle field (iOS) by @hramos in #7

New Contributors

• @hramos made their first contribution in #7

Full Changelog: v1.2.0...v1.3.0

What's Changed

• Add support for Laravel 10 by @mttlck in #6

New Contributors

• @mttlck made their first contribution in #6

Full Changelog: v1.1.0...v1.2.0

What's Changed

• Adding Laravel 9 support by @nicko170 in #5

Full Changelog: https://github.com/laravel-notification-channels/expo/commits/v1.1.0