Android push (Firebase Cloud Messaging HTTP v1).
Apple's APNs lives in gateway.push; this is its Android twin and the two
are dispatched on the registered device's :platform. Credentials are a
Google service-account JSON — from the macOS keychain (service vis-fcm,
account service_account), from the environment, or from a file under
~/.vis/fcm/. Key material is never returned, logged or sent over the wire.
Android push (Firebase Cloud Messaging HTTP v1). Apple's APNs lives in `gateway.push`; this is its Android twin and the two are dispatched on the registered device's `:platform`. Credentials are a Google service-account JSON — from the macOS keychain (service `vis-fcm`, account `service_account`), from the environment, or from a file under `~/.vis/fcm/`. Key material is never returned, logged or sent over the wire.
(config)Resolved FCM credentials WITHOUT key material: project id, the service account's email, where it came from, and what is still missing.
Resolved FCM credentials WITHOUT key material: project id, the service account's email, where it came from, and what is still missing.
(configured?)True when this gateway can actually deliver an Android push.
True when this gateway can actually deliver an Android push.
(dead-token? {:keys [status reason]})True when FCM's verdict means the registration is gone for good.
True when FCM's verdict means the registration is gone for good.
(send! token notification)Deliver one alert to one Android device token. Returns {:status int :reason str} — status 0 for a transport failure, so this never throws. A reason of
UNREGISTERED means the caller should drop the token.
Deliver one alert to one Android device token. Returns `{:status int :reason
str}` — status 0 for a transport failure, so this never throws. A `reason` of
`UNREGISTERED` means the caller should drop the token.cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |