Skip to content

Push apps: Settings → Push Apps, and pushes with each app's own keys - #436

Merged
roncodes merged 2 commits into
release/v0.7.2from
feat/push-apps
Nov 19, 2026
Merged

roncodes merged 2 commits into
release/v0.7.2from
feat/push-apps

Conversation

@roncodes

Copy link
Copy Markdown
Member

An organization's own apps (Passenger, a white-label driver app, an AppHelm build) now get Fleet-Ops pushes sent with their own Apple and Firebase credentials. The registry is core's PushApp (fleetbase/core-api#340); this adds the Fleet-Ops side.

  • Settings → Push Apps (fleet-ops/settings/push-apps, permissions view/update notification-settings): add, edit, turn off and remove push apps. Each has its key to copy into the app, its iOS bundle and Android project, and a device count. Keys are pasted in and never shown again; leaving one empty when editing keeps it. Send test push checks an app against one device token.
  • Register device: v1/customers/register-device and v1/drivers/register-device accept push_app (the key) and environment (production/sandbox). The device is linked to the app (PushAppDevices); a key that isn't one of the organization's active apps is refused.
  • Sending: the 10 push notifications (OrderUpdate, used by order config notify_customer/notify_driver, plus assigned, dispatched, canceled, completed, failed, changed, unassigned, ping, waypoint completed) add PushAppChannel. Driver and Contact route push-app devices to it and all other devices to the install-wide APNs/FCM channels, so Navigator and existing devices are unchanged and nothing is sent twice.
  • composer.json requires fleetbase/core-api ^2.0.3, so CI here stays red until core-api 2.0.3 (Release v2.0.3 core-api#339) is released.

Tests: server/tests/Unit/Support/PushAppsTest.php covers routing, device linking and every Settings endpoint branch; register-device tests cover the refused key.

…h their own keys

- Settings → Push Apps lists, adds, edits and removes the organization's push
  apps (APNs key and Firebase service account, written but never read back)
  and sends a test push to one device.
- v1/customers/register-device and v1/drivers/register-device accept
  push_app (the app's key) and environment, link the device to that app and
  refuse an unknown key.
- Every Fleet-Ops push notification also goes through core's PushAppChannel;
  Driver and Contact route push-app devices there and every other device to
  the install-wide APNs and FCM channels as before.
- Requires fleetbase/core-api ^2.0.3.
@roncodes roncodes mentioned this pull request Nov 18, 2026
- composer accepts dev-release/v2.0.3 next to ^2.0.3, and the contract run
  links core-api's release branch
- the service account placeholder no longer has braces, which ICU read as
  an argument and failed the Ember build
- install-wide token routes are plain lists, and the tests now expect that
@roncodes
roncodes merged commit 11bdaba into release/v0.7.2 Nov 19, 2026
5 of 6 checks passed
@roncodes
roncodes deleted the feat/push-apps branch November 19, 2026 04:29
@roncodes roncodes mentioned this pull request Nov 19, 2026
7 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant