@ctwillie Here is the start of my pull request. It still obviously needs a lot of work and I haven't added any testing yet, but feel free to look and offer feedback.

This PR fixes #7 and adds next features:

Ability to set a bunch of messages before making a request.

$messages = [];

$messages[] = (new ExpoMessage())
    ->setTitle('random title')
    ->setTo(['ExponentPushToken[vwskdcfnkal]', 'ExponentPushToken[kljmfwe32rklowm]']);

$messages[] = (new ExpoMessage())
    ->setTitle('another notification')
    ->setTo('ExponentPushToken[single-recipient]');

$messages[] = (new ExpoMessage())
    ->setTitle('notification with default recipients');

(new Expo())->send($messages)->to(['ExponentPushToken[default-recipients-here]'])->push();

Ability to pass array of data in both ExpoMessage constructor and Expo send() method, without creating instances manually.

$messages = [];

// ExpoMessage can be created automatiaclly
$messages[] = [
    'title' => 'test title',
    'body' => 'test body',
    'to' => 'ExponentPushToken[kjsdnfjkasnekf]',
    'data' => ['some' => 'data'],
];
// or be instantiated manually
$messages[] = (new ExpoMessage([
    'title' => 'Test not123123',
    'body' => 'Test body123123123',
]))->setTitle('this title will override initial one'),

(new Expo)->send($messages)->push();

Introduces two macros for handling tokens with DeviceNotRegistered errors.

You can register them somewhere in the beginning of request life cycle and its callbacks will be called for all invalid tokens.

Expo::addDevicesNotRegisteredHandler(function ($tokens) {
    // this callback is called once and it recieves array of invalid tokens
});
Expo::addDeviceNotRegisteredHandler(function ($token) {
    // this callback is called for each token separately and only if previous macro is not registered
});

I am sending this data via the SDK. I receive everything except for the categoryId as categoryIdentifier. Is there anything that I am doing wrong?

$messages = [
     'title'      => $notification['title'],
     'body'       => $notification['body'],
     'to'         => $notification['device_token'],
     'data'       => json_decode($notification['json_data'], true),
     'categoryId' => $notification['category_identifier'],
];

I even tried sending categoryIdentifier and category_identifier but again was not able to consume it in react native.

@ctwillie would you be willing to allow the DriverManager properties to protected rather than private? That way I can create my own DriverManager that extends yours and also create additional drivers for personal use.

Currently getting :

GuzzleHttp\Exception\RequestException : cURL error 60: SSL certificate problem: certificate has expired (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://exp.host/--/api/v2/push/send

using the basic example from docs, looks like some problem for expo.

using :

• php 7.4
• Latest version of your library

I'll provide a PR to fix this.

Hello,

Thanks for you SDK. I new with Expo and while I was accidently failing at trying to send a notification, I found this bug: when setting an empty array as data param, the API returns a 400 error:

[
  "errors" => [
    0 => [
      "code" => "VALIDATION_ERROR"
      "message" => ""[0].data" must be of type object."
      "isTransient" => false
    ]
  ]
]

However, the code was designed to handle a int, not a string. The documentation confirms this: https://docs.expo.dev/push-notifications/sending-notifications/#push-receipt-response-format

Error returned:

In ExpoErrorManager.php line 61:

  [TypeError]
  Exception::__construct(): Argument #2 ($code) must be of type int, string given

I thought it would be a good idea to prepend the stringed code to the error message to have some more context.

[ExpoSDK\Exceptions\ExpoException (400)]
  VALIDATION_ERROR: "[0].data" must be of type object.

Thanks!

Your package doesn't need the latest version of Guzzle and this will easier the way to add your package in an old project.

Thanks for this package, it's very useful.

@ctwillie I noticed that the ticket error details from the expo api now include expoPushToken at least when the type is DeviceNotRegistered. Thought it might be helpful to move in that direction.