expo-pusher-push-notifications 0.4.1 → 0.4.2

package/README.md

@@ -25,7 +25,7 @@ await Interests.start('YOUR_BEAMS_INSTANCE_ID');
 await Interests.subscribe('news');
 ```
 
-That device now gets anything your server publishes to `news`. Full console steps (APNs, Firebase, Beams) are in [Setup](docs/setup.md).
+That device now gets pushes sent to `news`. Full console steps (APNs, Firebase, Beams) are in [Setup](docs/setup.md).
 
 ## Subscribe to interests (topics)
 
@@ -40,16 +40,16 @@ More in [Interests](docs/interests.md).
 
 ## Bind a device to a user
 
-When your backend thinks in user ids ("send this to user-123"), bind the device to the signed-in user. Beams asks your API for an auth token, so you need one small endpoint on your server.
+To get pushes meant for a specific signed-in user on all their devices, bind the device to that user.
 
 ```ts
 import { Users } from 'expo-pusher-push-notifications';
 
 await Users.start('YOUR_BEAMS_INSTANCE_ID');
 
-// after your own sign-in
+// after your own sign-in (url = your Beams token provider)
 await Users.login('user-123', {
-  url: 'https://api.example.com/pusher/beams-auth',
+  url: 'YOUR_BEAMS_TOKEN_URL',
   headers: { Authorization: `Bearer ${sessionToken}` },
 });
 
@@ -57,17 +57,7 @@ await Users.login('user-123', {
 await Users.logout();
 ```
 
-You can use interests and users together. See [Authenticate users](docs/users.md) for the server side.
-
-## Send from your server
-
-```js
-import PushNotifications from '@pusher/push-notifications-server';
-const beams = new PushNotifications({ instanceId, secretKey });
-
-await beams.publishToInterests(['news'], payload);  // everyone on a topic
-await beams.publishToUsers(['user-123'], payload);  // one user, all their devices
-```
+You can use interests and users together. More in [Users](docs/users.md).
 
 ## Extras
 
@@ -86,7 +76,7 @@ Custom sounds go in the plugin's `sounds` option. Details in [Extras](docs/extra
 
 - [Setup](docs/setup.md)
 - [Interests](docs/interests.md)
-- [Authenticate users](docs/users.md)
+- [Users](docs/users.md)
 - [Sounds, channels, badges, local notifications](docs/extras.md)
 - [Full API](docs/api.md)
 - [Migrating from react-native-pusher-push-notifications](docs/migrating.md)

package/docs/extras.md

@@ -29,7 +29,7 @@ await Push.setBadgeCount(0);      // clear
 
 - **iOS:** uses the real app icon badge (`UNUserNotificationCenter.setBadgeCount`). Payloads can also set `aps.badge`.
 - **Android:** there is no system badge API. The module keeps a counter, applies it as the notification number on notifications it posts, and clears the shade when you set the count to `0`. Launchers show dots or counts based on the channel's `showBadge` setting.
-- **`incrementBadge` (from b8ne):** add `"incrementBadge": true` under `aps.data` or a top-level `data` (iOS), or `"incrementBadge": "true"` in FCM `data` (Android), and the badge goes up by one on the device. Your backend doesn't need to track counts.
+- **`incrementBadge` (from b8ne):** add `"incrementBadge": true` under `aps.data` or a top-level `data` (iOS), or `"incrementBadge": "true"` in FCM `data` (Android), and the badge goes up by one on the device.
 
 ## Local notifications
 

package/docs/interests.md

@@ -1,7 +1,6 @@
 # Interests (topics)
 
 Use interests when many devices should get the same push. Think topics: `news`, `order-42`, `team-7`.
-You need a Pusher Beams instance. Your server calls `publishToInterests`.
 
 ## Client
 
@@ -20,18 +19,6 @@ await Interests.clear();
 await Interests.reset();
 ```
 
-## Server (Node)
-
-```js
-import PushNotifications from '@pusher/push-notifications-server';
-const beams = new PushNotifications({ instanceId, secretKey });
-
-await beams.publishToInterests(['news'], {
-  apns: { aps: { alert: { title: 'Hi', body: 'News!' }, sound: 'ding.wav', badge: 3 } },
-  fcm: { notification: { title: 'Hi', body: 'News!', sound: 'ding', android_channel_id: 'messages' } },
-});
-```
-
 ## API
 
 | Call | What it does |

package/docs/migrating.md

@@ -21,7 +21,7 @@ Neither original had custom sounds, notification channels, or local and schedule
 
 ## Coming from 0.3
 
-0.4 removes raw device-token support (`DeviceToken`, `registerForDeviceToken`, `getDevicePushToken`, `deleteDevicePushToken`, and `mode: 'device'`). This package is Pusher Beams only now. If you need a raw FCM / APNs token for your own server, use [`expo-notifications`](https://docs.expo.dev/versions/latest/sdk/notifications/) and `getDevicePushTokenAsync()` instead.
+0.4 removes raw device-token support (`DeviceToken`, `registerForDeviceToken`, `getDevicePushToken`, `deleteDevicePushToken`, and `mode: 'device'`). This package is Pusher Beams only now. If you need a raw FCM / APNs token, use [`expo-notifications`](https://docs.expo.dev/versions/latest/sdk/notifications/) and `getDevicePushTokenAsync()` instead.
 
 ## Steps
 

package/docs/setup.md

@@ -52,7 +52,6 @@ The plugin also adds the `remote-notification` background mode on iOS. On Androi
 1. **iOS:** enable the Push Notifications capability. The plugin sets the entitlement. Create an APNs auth key (.p8).
 2. **Android:** create a Firebase project, download `google-services.json`, and point `android.googleServicesFile` at it.
 3. **Beams:** create a Beams instance in the [Pusher dashboard](https://dashboard.pusher.com/beams), then upload your APNs key and your FCM service account to it.
-4. **If you bind devices to users:** add an authenticated endpoint to your backend that returns `{ "token": beamsClient.generateToken(userId) }` (see the [Beams auth docs](https://pusher.com/docs/beams/guides/publish-to-specific-user/)).
 
 ## Permissions
 

package/docs/users.md

@@ -1,8 +1,6 @@
 # Bind a device to a user
 
-When your backend thinks in user ids ("send this to user-123"), bind the device to the signed-in user and Beams will deliver to every device they're signed in on.
-
-How it works: after your own sign-in, the app calls `Users.login(userId, …)`. Beams then asks **your API** for a short-lived auth token, which proves this user really is `user-123`. So you need one authenticated endpoint on your server.
+Bind the device to the signed-in user so pushes for that user reach every device they're signed in on. Call `Users.login` after your own sign-in, and `Users.logout` on sign-out.
 
 ## In the app
 
@@ -11,9 +9,9 @@ import { Users } from 'expo-pusher-push-notifications';
 
 await Users.start('YOUR_BEAMS_INSTANCE_ID');
 
-// After your own sign-in. Beams calls this URL and refreshes the token for you.
+// After your own sign-in. Pass your Beams token provider URL (and headers, if it needs them).
 await Users.login('user-123', {
-  url: 'https://api.example.com/pusher/beams-auth',
+  url: 'YOUR_BEAMS_TOKEN_URL',
   headers: { Authorization: `Bearer ${sessionToken}` },
 });
 
@@ -24,23 +22,6 @@ await Users.login('user-123', beamsToken);
 await Users.logout();
 ```
 
-## On your server (Node)
-
-```js
-// GET /pusher/beams-auth  (must be authenticated, and user_id must match the session)
-app.get('/pusher/beams-auth', requireSession, (req, res) => {
-  res.json(beams.generateToken(req.user.id)); // { token: '…' }
-});
-
-// Send
-await beams.publishToUsers(['user-123'], {
-  apns: { aps: { alert: { title: 'Hey', body: 'You have a new message' }, sound: 'ding.wav' } },
-  fcm: { notification: { title: 'Hey', body: 'You have a new message', android_channel_id: 'messages' } },
-});
-```
-
-See Pusher's [auth guide](https://pusher.com/docs/beams/guides/publish-to-specific-user/).
-
 ## API
 
 | Call | What it does |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "expo-pusher-push-notifications",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "Pusher Beams push notifications for Expo (interests and authenticated users), with custom sounds, Android channels, badges and local notifications",
   "main": "build/index.js",
   "types": "build/index.d.ts",