Note that when inspecting the info.plist in the IPAs on the backend, you need to inspect 2 keys, not one. First, CFBundleShortVersionString is the primary version number and CFBundleVersion is the secondary (build) number. For example, the version would be:
1.0.4 (32485)
You should always inspect CFBundleShortVersionString THEN CFBundleVersion when evaluating an update. You should also handle alphanumeric characters in the build version and rank those "alphanumerically" and based on "seen" date. This is how auto app works: a combination of release date and version inspection.
<key>CFBundleShortVersionString</key>
<string>1.0.4</string>
<key>CFBundleVersion</key>
<string>32485</string>
So build 32485z would be newer than build 32484z. Release date should take priority if you have two versions with different build numbers. Check which was more recently seen.
This manifest file is served on an easily reconfigurable static URL. The purpose is to update the redirect file that powers this static URL to point it at various manifest & by proxy IPA versions to simulate a customer "updating" an app by updating their manifest file located at a static URL.
The current version being served by the static URL is:
Fetching...
To update the version served, update the Sammy hosting repo (Reach out to @dtnb).
ITMS link:
Fetching...