Update: Our auth provider says their database restoration will take several hours. It appears they’re restoring the entire database of all Expo developer accounts, which is why it’s taking this much time. Unfortunately, there’s nothing we can do to re-enable login while our auth provider is restoring their database.
Some positive news: We’ve made a backup of accounts that were newly created or edited within the last 24 hours. This means that if our auth provider doesn’t restore those accounts (their backup is one day old), we have that data and will attempt to restore it ourselves.
What you can do until then: As mentioned above, our
exp command-line program supports an offline mode while developing. Run
exp start --offline for example. Offline mode is very similar to regular mode, except that some APIs like AsyncStorage will behave differently (you will not be able to access previously stored data).
What’s next: It’s past 1AM here right now so I’m going to sign off in a bit and be online around 7AM PDT to check on the progress of the database restoration. Assuming it’s complete, we’ll update this topic to let you know that fixing this issue is no longer blocked on our auth provider. We plan to restore data from our own backup as mentioned above, and if everything looks good we’ll re-enable logging in and developer account services and update this topic again.
We totally get how unexpected and distracting this issue could be and are really sorry it happened and we couldn’t fix it more quickly.