Expo: Newly built standalone apps for iOS do not register for push notifications
Timeline of updates
- resolved
We've deployed an update to the iOS standalone app builders that fixes this issue. This incident affected only IPAs built with
exp build:iosbetween 2018-01-22 4:30pm to 2018-01-27 10:05pm (Pacific time). This incident did not affect any previously built IPAs, including IPAs that developers may have published to the App Store. New standalone apps whose builds started after 2018-01-27 at 10:05pm Pacific time will include the new code that correctly registers for push notifications. Developers who have created builds affected by this incident will need to create new IPAs. You can get a new standalone app IPA by runningexp build:ios. Make sure to bump your IPA's version number so that you can submit the new build to TestFlight (ios→buildNumberin app.json might help: https://docs.expo.io/versions/latest/guides/configuration.html#buildnumber (opens in new tab)).
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 2018-01-28 00:40 UTC, resolved after 6.1 h, 1 update(s).
- Title
- Newly built standalone apps for iOS do not register for push notifications
- Vendor
- Expo
- Date
- URL
- https://rewindex.com/company/expo/incidents/z2761rqdd4w1
Expo profileRecent Expo incidentsAll outages on January 28, 2018Expo in January 2018MarkdownJSON