I understand that you are frustrated, but calling it “BS” is not a professional or fair way to describe the factual state of things related to the App Store reality.
This has already been explained several times: we cannot provide guaranteed rollbacks for App Store builds because Apple does not provide a developer-controlled rollback mechanism. TestFlight is not a production rollback system either. Builds expire, availability is limited, and it is intended for testing, not for maintaining old production versions on demand. Period.
For mission-critical setups, we have repeatedly recommended the same workflow:
- turn off automatic App Store automatic updates
- make a full local iPad backup before installing a major update
- update outside active project deadlines
- send logs immediately if something goes wrong
That is the only reliable way to protect a production iPad before updating. We cannot change how App Store distribution works.
If 1.6.19 is stable for your current work, staying on it for now is completely reasonable. But presenting the lack of App Store rollbacks as something we simply refuse to provide is inaccurate, and calling it “BS” does not help us diagnose or fix anything.