What is the logic of version number and build number in TestFlight In-App Updates? TF states that the build number must be larger so that the "In-App Update" popup appears and happens, but always reset the build number when I increment / increment the version number.
If I change the value from v1.0.0 (2)→ v1.0.1 (1), will this allow me to upgrade the In-App? Or I need to do an update v1.0.1 (3). Having a build number 3doesn’t work well with my OCD, since I appreciate the availability of reasonable numbers in my build histories. I would really like to see something in the lines v2.0.0 (547).
I understand that I could increase the build number in tandem with my version number better ( v1.2.3 (123)), but there are potential problems, such as v1.2.34 (1234)with a higher build number than v1.3.0 (130).
I release it for clients, so it’s inconvenient for me to test this, and I use the company’s developer account, so creating random test applications will probably not look great either. Hopefully someone might have an easy answer to my request, and I changed my mind about all this.
I hope this question can be asked. Based on the FAQ, I should be fine to ask about software tools commonly used by programmers, but I was persecuted to ask about TestFlight earlier.
source
share