Is it possible that we pushed out an OTA update without doing expo publish? I’ve never used that command, and we are in the middle of testing an update. And all of a sudden our users have this broken in-progress update. I hadn’t even created a build. All I’d done is push code to the git repo.
We don’t want to use OTA updates at all (did not realize it was enabled by default), and all of a sudden we’re accidentally sending them.
I just did expo publish to try and force an OTA update with a fix to the problematic build that was inadvertently sent out. But the update hasn’t pushed to my device. Not sure if there’s a delay.
This is such a strange issue. I would never have expected all our users to get a code update without publishing or building anything.