agilicent/laravel-expo-push-notifications

Laravel Notifications driver for Expo Push Notifications

Laravel Expo Push Notifications

An Expo Push Notifications driver for Laravel Notifications.

Automatically expires PushTokens if they fail due to DeviceNotRegistered error, and won't use them again.

Stores data about Push Notification delivery status.

Installation

Via Composer

$ composer require relative/laravel-expo-push-notifications

Run migrations

$ php artisan migrate

Optional: Publish migrations & configuration

$ php artisan vendor:publish --provider="Relative\LaravelExpoPushNotifications\ExpoPushNotificationsServiceProvider"

If you use UUIDs for your model id fields, publish the migrations and follow the instructions in the file to switch to string id columns.

Usage

Setup your notifiable users

To get started, add the HasPushTokens trait to your notifiable class(es), e.g. your App\User model

<?php

use Relative\LaravelExpoPushNotifications\Traits\HasPushTokens;

class User {
    use Notifiable, HasPushTokens;
    
    //
}

Register Push Tokens to your users

Your Expo app will be able to generate a Push Token and POST it to a controller method in your Laravel application, which can then register the token to that user, for example:

<?php

class PushNotificationController extends \Illuminate\Routing\Controller {

    public function register(Request $request)
    {
        $token = $request->input('token');
        $request->user()->pushTokens()->firstOrCreate(
            ['token' => $token],
            ['token' => $token],
        );
        return response()->status(200);
    }

}

Notify a user about something

Add ExpoPushNotifications to your Notifiable object

<?php

use Illuminate\Bus\Queueable;
use Relative\LaravelExpoPushNotifications\ExpoPushNotifications;
use Relative\LaravelExpoPushNotifications\PushNotification;

class NewOrder extends \Illuminate\Notifications\Notification {

    use Queueable;
    
    public $order;

    /**
     * Create a new notification instance.
     *
     * @param $order
     */
    public function __construct($order)
    {
        $this->order = $order;
    }

    /**
     * Get the notification's delivery channels.
     *
     * @param mixed $notifiable
     * @return array
     */
    public function via($notifiable)
    {
        return [ExpoPushNotifications::class];
    }

    public function toExpoPushNotification($notifiable)
    {
        return (new PushNotification)
            ->title('New order received')
            ->body("Order #{$this->order->id} is ready for processing");
    }

}

The constructor of the PushNotification class accepts an array of parameters matching the schema defined here: https://docs.expo.io/push-notifications/sending-notifications/#message-request-format

Alternatively you can use the expressive API, in Laravel style as shown above.

The PushNotification class has constants for the priority and sound parameters:

PushNotification::PRIORITY_HIGH;
PushNotification::PRIORITY_NORMAL;
PushNotification::PRIORITY_DEFAULT;

PushNotification::SOUND_DEFAULT;
PushNotification::SOUND_NONE;

Change log

Please see the changelog for more information on what has changed recently.

Testing

$ composer test

Contributing

Please see contributing.md for details and a todolist.

Security

If you discover any security related issues, please email author email instead of using the issue tracker.

Credits

• Nick Cousins
• Relative
• All Contributors

License

MIT License. Please see the license file for more information.

laravel-expo-push-notifications's Issues

Add a 'read' status to messages

To complete the package we could add a timestamp for 'read_at' to the notifications, which could then be called from a controller method when anyone wants to implement a notification centre in their app. Pulling notifications from the database is currently very easy but if we had a "read" field, we could then manage the badge on iOS too if we wanted.

This property is missing from the migrations.

This property is missing from the migrations.

https://github.com/relativelimited/laravel-expo-push-notifications/blob/75c154ac3e70102e00fb7064b1da9a37d3a97818/src/ExpoPushNotifications.php#L81

Package requires unit tests

We need to add unit tests to cover the entire package, right now there are none.

Support for Laravel 9

Hi,
would this package be available for laravel 9?

Need to add configurable defaults

Ideally, the package should allow all fields, except title, subtitle, body and data to have configurable defaults in case users want a standard TTL, or sound setting for example for all notifications sent from their app.

Undefined array key "6b158d5c-78bc-407b-a837-4f5a6a471571"

I am getting this error referencing this line:

laravel-expo-push-notifications/src/ExpoPushNotifications.php

Line 104 in 24e9cb7

$pushNotification->errors = $receipts[$pushNotification->ticket]['details']['error'];

This is strange since ticket 6b158d5c-78bc-407b-a837-4f5a6a471571 doesn't have an error. This is the receipt:

{
  "data": {
    "5078bd5a-de49-4ca2-91a3-ce15573febaa": {
      "status": "ok"
    },
    "6b158d5c-78bc-407b-a837-4f5a6a471571": {
      "status": "ok"
    },
    "91fd968a-e585-46c9-84cd-88fbf220ac9f": {
      "status": "error",
      "message": "Unable to retrieve the FCM server key for the recipient's app. Make sure you have provided a server key as directed by the Expo FCM documentation.",
      "details": {
        "fault": "developer",
        "error": "InvalidCredentials",
        "sentAt": 1650455334
      },
      "__debug": []
    }
  }
}