Could I clarify how eas build iteracts with ota updates
I have an app available with installed users on the App Store.
I ran a new build yesterday with some changes on the production release channel. My intention was to test this build on TestFlight before releasing it the App Store. As it turned out, there are some issues with this new build so I don’t want to release it to the App Store.
I was surprised to discover that some of my users now have the latest update on the app on their phone. I can see that the app installed on their phone reports to be the expected version (the version available on the App Store), yet the app which they are interacting with is definitely the latest build which should not be available on the App Store.
My initial explanation for this was that an update had been published to the release channel when eas build ran (even though I was under the understanding that this did not happen). I then tried to run another build with the old version of the code in the hope of overwriting the incorrect version but this does not seem to have changed anything and when performing a fresh install from the App Store of the old version, I am still getting the new version.
Are you able to confirm whether running eas build triggers an OTA update? If not, can you give insights into what is happening here and how I can rectify the problem?