TIL more about Expo Fingerprints for EAS updates.
The ability to compare a fingerprint in the web UI is a critical tool for debugging, and we were able to use it to identify that we were using EAS Environments wrong.
I had set up some of our automatic update workflows to publish on a preview channel, thinking it would inherit our preview configuration, but that’s not how it works. The right way to do it is to set our ENV variables in Expo, and then depend on the environment for builds and publishing updates so that our update matched our build.
Once we get that sorted, we should be back on the golden path. This will help as we keep moving our OTA update strategy forward.