Expo: Sending FCM Push Notifications Results in an INVALID_CREDENTIALS Error
Timeline of updates
- resolved
Issue identified at Jul 18, 08:35 PDT. Upon sending an Android push notification, FCM responded with an INVALID_CREDENTIALS error. This was correlated with an issue with Expo CLI where attempting to upload an FCM server key resulted in an Unknown error. The fix for both of these issues landed in production. You should be able to send FCM push notifications and upload FCM keys to our servers without problems. Thank you for your patience! Resolved at Jul 18, 10:42 PDT.
From Expo’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.expo.dev (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Expo, started 2019-07-26 21:12 UTC, resolved after 0 min, 1 update(s).
- Title
- Sending FCM Push Notifications Results in an INVALID_CREDENTIALS Error
- Vendor
- Expo
- Date
- URL
- https://rewindex.com/company/expo/incidents/5npr4ryqd4y3
Expo profileRecent Expo incidentsAll outages on July 26, 2019Expo in July 2019MarkdownJSON