We've deployed an update to the iOS standalone app builders that fixes this issue.
This incident affected only IPAs built with `exp build:ios` between 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.
Standalone iOS apps that were built in the past few days do not register their native device tokens with the Expo push service. This affects apps that were recently built for iOS that use push notifications. If your app is Android-only, was built before last week, or does not use push notifications, it is not affected.
If you do plan to create an iOS app with "exp build:ios" that uses push notifications, please wait until this issue is resolved.
Symptoms: if you get an Expo push token from an affected standalone app and send a notification to it, the Expo push service will respond with an error of the form:
{
"status": "error",
"message": "The recipient \"ExponentPushToken[xxx]\" isn't associated with any device",
"details": { "error": "DeviceNotRegistered" }
}