PHPackages                             potagercity/expo-notifications-bundle - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. potagercity/expo-notifications-bundle

ActiveSymfony-bundle

potagercity/expo-notifications-bundle
=====================================

Bundle to handle the BE tasks of the push notifications service for the expo react-native Framework. fork from solvecrew one

1.2.1(7y ago)06MITPHPPHP >=7.0

Since Aug 29Pushed 6y agoCompare

[ Source](https://github.com/potagercity/ExpoNotificationsBundle)[ Packagist](https://packagist.org/packages/potagercity/expo-notifications-bundle)[ Docs](http://solvecrew.github.com)[ RSS](/packages/potagercity-expo-notifications-bundle/feed)WikiDiscussions develop Synced 1mo ago

READMEChangelogDependencies (11)Versions (7)Used By (0)

README
======

[](#readme)

This Bundles purpose is to handle the BE tasks of the push notifications service for the expo react-native Framework.

Installation
============

[](#installation)

Install the bundle using composer:

```
composer require solvecrew/expo-notifications-bundle

```

Enable the Bundle in the app/AppKernel.php file:

```
$bundles = [
    ...
    new Solvecrew\ExpoNotificationsBundle\SCExpoNotificationsBundle(),
    ...
];

```

Configuration
=============

[](#configuration)

At the moment, this bundle only has a single optional configuration parameter.

If you want (optional), add this to your `app/config/config.yml` file:

```
sc_expo_notifications:
    expo_api_endpoint: '%expo_api_endpoint%'

```

And then add the `expo_api_endpoint` parameter in your `app/config/parameters.yml` file:

```
expo_api_endpoint: https://exp.host/--/api/v2/push/send

```

If you prefer to not add it as a parameter in your `parameters.yml` file you can add the URI in your config.yml file directly:

```
sc_expo_notifications:
    expo_api_endpoint: https://exp.host/--/api/v2/push/send

```

**IMPORTANT**: All this is completely OPTIONAL. If you don't add the config at all, it will use `https://exp.host/--/api/v2/push/send` as fallback since it is the endpoint from the official Expo Documentation.

Usage
=====

[](#usage)

This bundle provides you with an easy way to send push notifications for a front-end application using the Expo React-Native framework. Therefore the bundle provides you with several helpful things:

- NotificationContentModel: A model representing the requestdata for a single notification. As specified by the Expo API.
- NotificationManager: A Manager to handle the preparing of the notification, the sending and the reponse.

The service of the NotificationManager is `sc_expo_notifications.notification_manager`.

- Use it in a controller with `$this->container->get('sc_expo_notifications.notification_manager')`.
- Inject it as a dependency like:

```
app.example_manager:
    class: AcmeBundle\Manager\ExampleManager
    arguments: ['@sc_expo_notifications.notification_manager']

```

NOTE that the important part here is the `arguments: ['@sc_expo_notifications.notification_manager']` of course.

After you have the NotificationManager available you can access its functions. Popular functions are:

1. sendNotifications(...): Send multiple notifications in one API request.

```
    /**
     * Handle the overall process of multiple new notifications.
     *
     * @param array $messages
     * @param array $tokens
     * @param array $titles
     * @param array $data
     *
     * @return array
     */
    public function sendNotifications(
        array $messages,
        array $tokens,
        array $titles = [],
        array $data = []
    ): array
    {
		...
    }

```

Therefore you need to provide an array of `messages` as strings and an array of `tokens` as strings (to be more specific: The recipients ExponentPushToken. Like `sITGtlHf1-mSgUyQIVbVMJ`, without the `ExponentPushToken[]`sourrounding.). The first message in the messages array will be delivered to the first token (recipient) in the tokens array. And so on. Optionally you can provide a `titles` array which holds titles for the notifications. Last, you can provide an array of data arrays that will be added to the notification as a JSON object for further handling in the front-end. It is important to know, that each notification needs an array as data! See the Full Example below for more information.

The function returns you an array of NotificationContentModel. One for each notification that was tried to send. Those NotificationContentModels hold all the information about the notification.

For example:

- to: The token that represents the recipient.
- title: The title, if provided.
- body: The actual message of the notification.
- wasSuccessful: A boolean indicating whether the notification was send (does NOT mean it was recieved or viewed).
- responseMessage: A message that was returned by the Expo API on unsuccessful request for the specific notification.
- responseDetails: An array holding error specific information.

2. sendNotification(...): Send a single notification providing only a message string and a token. Optionally a title.

```
    /**
     * Handle the overall process of a new notification.
     *
     * @param string $message
     * @param string $token
     * @param string $title
     * @param array $data
     *
     * @return array
     */
    public function sendNotification(
        string $message,
        string $token,
        string $title = '',
        array $data = null
    ): NotificationContentModel
    {
		...
    }

```

As you can see, this one is really straight forward. It returns a single NotificationContentModel as descibed above. The title (string) and the data (array) are optional. If provided, $data must be an array.

Full Example
------------

[](#full-example)

To even ease the integration process further, see the following example.

```
// Get an instance of the NotificationManager provided by this bundle.
// Using the service, that is available since the bundle installation.
// Better would be to inject the service as a dependency in your service configuration.
$notificationManager = $this->get('sc_expo_notifications.notification_manager');

// Prepare the titles as you wish. If none would be provided, the app name will be a fallback by Expo.
$titles = [
    'New Notification',
    'Hot news',
];

// Prepare the messages that shall be sent. This will be more sophisticated under realistic circumstances...
$messages = [
    'Hello there!',
    'What's up?!',
];

// Prepare the ExpoPushTokens of the recipients.
$tokens = [
    'H-Dsb2ATt2FHoD_5rVG5rh',
    'S_Fs-1ATt4AHDD_5rXcYr4',
];

// Prepare the data that you want to pass to the front-end to help you handle the notification.
$data = [
	['foo' => 'bar', 'baz' => 'boom'],
	['whatever' => 'you', 'want' => 'here'],
];

// Send the notifications using the messages and the tokens that will receive them.
$notificationContentModels = $notificationManager->sendNotifications(
    $messages,
    $tokens,
    $titles,
    $data
);

// Handle the response here. Each NotificationContentModel in the $notificationContentModels array
// holds the information about its success/error and more detailed information.

```

If your use case is more complex or you just want to leverage more of the notification funtions you can use the `sendNotificationHttp` function of the NotificationManager. For that you need to create the NotificationContentModel yourself.

```
// Use statement for the NotificationContentModel.
use Solvecrew\ExpoNotificationsBundle\Model\NotificationContentModel;

// Get an instance of the NotificationManager provided by this bundle.
// Using the service, that is available since the bundle installation.
// Better would be to inject the service as a dependency in your service configuration.
$notificationManager = $this->get('sc_expo_notifications.notification_manager');

$token = 'H-Dsb2ATt2FHoD_5rVG5rh';
$message = 'The message of the notification.';
$data = ['foo' => 'bar'];

$notificationContentModel = new NotificationContentModel();
$notificationContentModel
    ->setTo($token)
    ->setBody($message)
    ->setData($data)
    ->setPriority('medium');

// Send the notification.
$httpResponse = $notificationManager->sendNotificationHttp($notificationContentModel);

// Handle the response using the notificationManager. Enriches the NotifcationContentModel with the http response data.
$notificationContentModel = $notificationManager->handleHttpResponse($httpResponse, [$notificationContentModel]);

```

If you want to send multiple notifications this way, use `sendNotificationsHttp` (plural).

```
// Use statement for the NotificationContentModel.
use Solvecrew\ExpoNotificationsBundle\Model\NotificationContentModel;

// Get an instance of the NotificationManager provided by this bundle.
// Using the service, that is available since the bundle installation.
// Better would be to inject the service as a dependency in your service configuration.
$notificationManager = $this->get('sc_expo_notifications.notification_manager');

$data = ['foo' => 'bar'];

// Create a NotificationContentModel
$notificationContentModel = new NotificationContentModel();
$notificationContentModel
    ->setTo('H-Dsb2ATt2FHoD_5rVG5rh')
    ->setBody('test message')
    ->setData($data)
    ->setPriority('low');

// Create a second NotificationContentModel
$anotherNotificationContentModel = new NotificationContentModel();
$anotherNotificationContentModel
    ->setTo('Z-5sb2AFt2FHoD_5rVG5rh')
    ->setBody('Your message here')
    ->setData($data)
    ->setPriority('medium');

$notificationContentModels = [
    $notificationContentModel,
    $anotherNotificationContentModel,
];

// Send the notifications.
$httpResponse = $notificationManager->sendNotificationsHttp($notificationContentModels);

// Handle the response using the notificationManager. Enriches the NotifcationContentModel with the http response data.
$notificationContentModels = $notificationManager->handleHttpResponse($httpResponse, $notificationContentModels);

// The notificationContentModels have now been updated. The info for each notification is now stored in each model.

```

Troubleshooting
===============

[](#troubleshooting)

If the service `sc_expo_notifications.notification_manager` is not available for some reason, debug your container with `bin/console debug:container | grep notification`. You should see:

```
sc_expo_notifications.guzzle_client                GuzzleHttp\Client
sc_expo_notifications.notification_manager         Solvecrew\ExpoNotificationsBundle\Manager\NotificationManager

```

The first service is the guzzle client which is the dependency of our bundle. The second service is the notificationManager the bundle provides to handle all notification related tasks.

Based on the Expo push notifications API
========================================

[](#based-on-the-expo-push-notifications-api)

To see the process and the API documentation for the Expo push notifications service see:

LICENSE
=======

[](#license)

Created by SolveCrew 2017. Contact us if you like:  or visit our website: [www.solvecrew.com](http://www.solvecrew.com)MIT

###  Health Score

26

—

LowBetter than 43% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity4

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity62

Established project with proven stability

 Bus Factor1

Top contributor holds 65.2% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~191 days

Total

4

Last Release

2603d ago

PHP version history (2 changes)1.0.0PHP >=5.6

1.2.0PHP >=7.0

### Community

Maintainers

![](https://www.gravatar.com/avatar/4549bbd0738ce1e632c1a195091bc164b5e027b0dab7faeb671389587f4a8dcb?d=identicon)[potagercity](/maintainers/potagercity)

---

Top Contributors

[![yanc3k](https://avatars.githubusercontent.com/u/15339316?v=4)](https://github.com/yanc3k "yanc3k (15 commits)")[![solvecrew](https://avatars.githubusercontent.com/u/30549204?v=4)](https://github.com/solvecrew "solvecrew (5 commits)")[![chriskaya](https://avatars.githubusercontent.com/u/4079132?v=4)](https://github.com/chriskaya "chriskaya (2 commits)")[![lauzel](https://avatars.githubusercontent.com/u/9590565?v=4)](https://github.com/lauzel "lauzel (1 commits)")

---

Tags

push notificationsexpo

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/potagercity-expo-notifications-bundle/health.svg)

```
[![Health](https://phpackages.com/badges/potagercity-expo-notifications-bundle/health.svg)](https://phpackages.com/packages/potagercity-expo-notifications-bundle)
```

###  Alternatives

[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.4k5.6M650](/packages/sylius-sylius)[shopware/platform

The Shopware e-commerce core

3.3k1.5M3](/packages/shopware-platform)[drupal/core

Drupal is an open source content management platform powering millions of websites and applications.

19462.3M1.3k](/packages/drupal-core)[sulu/sulu

Core framework that implements the functionality of the Sulu content management system

1.3k1.3M152](/packages/sulu-sulu)[simplesamlphp/simplesamlphp

A PHP implementation of a SAML 2.0 service provider and identity provider.

1.1k12.4M193](/packages/simplesamlphp-simplesamlphp)[ec-cube/ec-cube

EC-CUBE EC open platform.

78527.0k1](/packages/ec-cube-ec-cube)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)