Download the PHP package ctwillie/expo-server-sdk-php without Composer

On this page you can find all versions of the php package ctwillie/expo-server-sdk-php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of ctwillie/expo-server-sdk-php

Informations about the package expo-server-sdk-php

expo-server-sdk-php tests codecov GitHub

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](#testing) - [Installation](#installation) - [Use Cases](#use-cases) - [Composing a Message](#composing-a-message) - [Sending a Message](#sending-a-push-notification) - [Channel Subscriptions](#channel-subscriptions) - [Expo Responses](#expo-responses) - [Handling Unregistered Devices](#handling-unregistered-devices) - [Retrieving Push Receipts](#retrieving-push-receipts) - [Changelog](#changelog) - [Contributing](#contributing) - [License](#license)

Testing

You can run the test suite via composer:

Installation

You can install the package via composer:

Use Cases

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

  1. Sending push notification messages to one or more recipients, then you're done! The most obvious use case.
  2. 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.

Sending a push notification

Compose a message then send to one or more recipients.

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.

:warning: 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.

Expo responses

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

Handling unregistered devices

Expo provides a macro for handling tokens that have DeviceNotRegistered error in the Expo response. You can register a callback before sending your messages to handle these unregistered tokens.

You only need to register the handler once as it will be applied to all Expo instances.

Retrieving push receipts

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

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.

Credits

All versions of expo-server-sdk-php with dependencies

PHP Build Version
Package Version
Requires php Version >=7.3
guzzlehttp/guzzle Version ^6|^7
ext-json Version *
ext-zlib Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package ctwillie/expo-server-sdk-php contains the following files

Loading the files please wait ....