Who owns what
The node never receives your
.p8 or FCM JSON. It never generates
ExponentPushToken[…]. Only the install does (via Expo SDK / native APIs).
Register
After pair + notification permission:- Obtain an Expo push token for your EAS
projectId. POST /papi/push-tokenwith{"token":"ExponentPushToken[…]"}(device-signed).- Re-register on cold start, when returning to foreground, and when the OS rotates the token.
- Clear with
{"token":""}on logout / remove-device (best effort).
Payload contract
When an approval is created, the node sends Expo a message whosedata is only:
kind: "test" and
approval_id: "ap_test_push". Show “push works”; do not open a fake approval.
On receive / tap
Multi-app on one node
A node fans out to every paired device with a non-empty token. Your app and another vendor’s app can both be paired; each has its owndevice_id and Expo token. Expo
routes each token to the correct APNs credentials automatically.
There is no per-app filter on the node today: every registered phone gets every approval
wake. Design for that (or only pair one approval app per household).
Credentials setup (Expo)
Fallback
Always poll. Push delay, denied permission, or Expo downtime must not strand approvals.Dead tokens
Nodes clear tokens when Expo reportsDeviceNotRegistered (and similar) on tickets or
receipts. Your app should simply register a fresh token after reinstall.