README

Server-side library for working with Expo using PHP.

If you have any problems with the code in this repository, feel free to open an issue or make a PR!

Table of Contents

Testing
Installation
Use Cases
Composing a Message
Sending a Message
Channel Subscriptions
Expo Responses
Retrieving Push Receipts
Changelog
Contributing
License

Testing

You can run the test suite via composer:

composer test

Installation

You can install the package via composer:

composer require ctwillie/expo-server-sdk-php

Use Cases

This package was written with two main use cases in mind.

Sending a push notification message to one or more recipients, then your done! The most obvious use case.
And channel subscriptions, used to subscribe one or more tokens to a channel, then send push notifications to all tokens subscribed to that channel. Subscriptions are persisted until a token unsubscribes from a channel. Maybe unsubscribing upon the end users request.

Keep this in mind as you decide which is the best use case for your back end.

Composing a message

Compose a push notification message to send using options from the Expo docs.

$message = (new ExpoMessage())
    ->setTitle('Message Title')
    ->setSubtitle('Message sub title')
    ->setBody('The notification message body')
    ->setChannelId('default')
    ->setBadge(0)
    ->playSound();

Sending a push notification:

Compose a message then send to one or more recipients.

$expo = new Expo();

// composed message, see above
$message;

$recipients = [
    'ExponentPushToken[xxxx-xxxx-xxxx]',
    'ExponentPushToken[yyyy-yyyy-yyyy]'
];

$expo->send($message)->to($recipients)->push();

Channel subscriptions:

Subscribe tokens to a channel, then push notification messages to that channel. Subscriptions are persisted internally in a local file so you don't have to worry about this yourself. Unsubscribe the token from the channel at any time to stop messages to that recipient.

⚠️ If you are are running multiple app servers: Be very careful here! Channel subscriptions are stored in an internal local file. Subscriptions will not be shared across multiple servers. Database drivers coming in the near future to handle this use case.

/**
 * Specify the file driver to persist subscriptions internally.
 * More drivers coming soon, (database, redis, custom local file)
 */
$expo = Expo::driver('file');

// composed message, see above
$message;

$recipients = [
    'ExponentPushToken[xxxx-xxxx-xxxx]',
    'ExponentPushToken[yyyy-yyyy-yyyy]'
];

// name your channel anything you'd like
$channel = 'news-letter';
// the channel will be created automatically if it doesn't already exist
$expo->subscribe($channel, $recipients);

$expo->send($message)->toChannel($channel)->push();

// you can unsubscribe one or more recipients from a channel.
$expo->unsubscribe($channel, $recipients);

Expo responses

Get the data returned from successful responses from the Expo server.

$response = $expo->send($message)->to($recipients)->push();

$data = $response->getData();

Retrieving push receipts

Retrieve the push receipts using the ticket ids from the Expo server.

$ticketIds = [
    'xxxx-xxxx-xxxx-xxxx',
    'yyyy-yyyy-yyyy-yyyy'
];

$response = $expo->getReceipts($ticketIds);
$data = $response->getData();

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

License

The MIT License (MIT). Please see License File for more information.

luniumall / expo-server-sdk-php

Maintainers

Details