@freecorps/ember-push 0.5.0 → 0.5.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -178,7 +178,11 @@ Device side: [`@freecorps/ember-expo-push`](../expo-push/README.md).
|
|
|
178
178
|
`outboundService` routes every `fetch` to the fakes: `sendNow` from an action, and `push.send` from a mutation
|
|
179
179
|
delivered by the shard's alarm.
|
|
180
180
|
|
|
181
|
-
## Real-device testing
|
|
181
|
+
## Real-device testing
|
|
182
|
+
|
|
183
|
+
Status: the token layer was proven on devices through Freecorps Brigade (2026-11-06; PLAN R12). The full path (the
|
|
184
|
+
`ember` envelope, the extension, the component) runs on Freecorps' mail app (freecorps/mail) since 2026-11-09; its
|
|
185
|
+
device results go to PLAN R12.
|
|
182
186
|
|
|
183
187
|
What you need:
|
|
184
188
|
1. **Apple:** a paid Apple Developer account, and your **Team ID** (developer.apple.com → Membership).
|
|
@@ -189,6 +193,14 @@ What you need:
|
|
|
189
193
|
(`group.<bundle id>.ember`) and, for `urgency: "high"`, *Time Sensitive Notifications*. The extension's App ID is
|
|
190
194
|
`<bundle id>.EmberNotificationService`, with the same App Group. EAS Build creates and syncs these from the
|
|
191
195
|
entitlements and the `appExtensions` entry the plugin writes. With local Xcode signing, enable them by hand.
|
|
196
|
+
Seen on the mail app's first build (2026-11-09):
|
|
197
|
+
- Signed in with an App Store Connect API key only, EAS turns *App Groups* on but cannot create the group. The
|
|
198
|
+
build then fails with "Provisioning profile … doesn't support the group.… App Group". Run the first `eas build`
|
|
199
|
+
signed in to the Apple account once, so EAS creates and links `group.<bundle id>.ember` and refreshes both
|
|
200
|
+
profiles. Later builds can use the key.
|
|
201
|
+
- The App Store Connect API has no Time Sensitive capability, so EAS's sync fails on it with a key. Set
|
|
202
|
+
`timeSensitive: false` in the plugin options if the app never sends `urgency: "high"`, or enable it in the
|
|
203
|
+
developer portal by hand.
|
|
192
204
|
4. **Firebase:** a project with an Android app for your package name. Download `google-services.json` (outside the
|
|
193
205
|
repository) and point `android.googleServicesFile` (or `GOOGLE_SERVICES_JSON` in the example) at it.
|
|
194
206
|
5. **FCM service account:** in Google Cloud IAM for that project, create a service account with role *Firebase Cloud
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@freecorps/ember-push",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.2",
|
|
4
4
|
"description": "Push notifications for Ember: device registry, Expo Push, direct APNs + FCM, end-to-end encrypted payloads (HPKE), and a push component.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"apns",
|
|
@@ -45,7 +45,7 @@
|
|
|
45
45
|
"access": "public"
|
|
46
46
|
},
|
|
47
47
|
"dependencies": {
|
|
48
|
-
"@freecorps/ember-server": "0.5.
|
|
49
|
-
"@freecorps/ember-values": "0.5.
|
|
48
|
+
"@freecorps/ember-server": "0.5.2",
|
|
49
|
+
"@freecorps/ember-values": "0.5.2"
|
|
50
50
|
}
|
|
51
51
|
}
|