Hello, I’m looking for clarification and guidance regarding a recent App Store Connect upload validation change that is preventing us from delivering an important bug-fix update to existing users on legacy iOS versions. Our production iOS app has historically supported iOS 11 and later. On August 28, 2026, we successfully uploaded a build with: MinimumOSVersion = 11.0 The upload completed successfully, with warnings only. One of the warnings stated: “MinimumOSVersion too low. This app has a MinimumOSVersion of 11.0. Starting later this year, all iOS apps must have a MinimumOSVersion of 13.0 or later in order to be uploaded to App Store Connect or submitted for distribution.” No specific enforcement date was provided. The same upload also displayed another warning stating: “Starting in Spring 2027, all iOS apps must have a MinimumOSVersion of 15.0 or later…” We subsequently uploaded another build targeting iOS 11 around September 8, and that version was successfully released on the App Store on September 10, 2026. I no longer have a screenshot of the warning from that particular upload, but the build itself was accepted and the corresponding version was released successfully. However, on September 17, 2026, when attempting to upload our next bug-fix build with the same MinimumOSVersion of 11.0, Apple’s server-side validation rejected the build with: Error 90068 “This bundle is invalid. The value provided for the key MinimumOSVersion '11.0' is not acceptable.” This means that the server-side enforcement appears to have changed sometime after our successful upload around September 8 and before September 17. What is especially confusing is that:
- the previous warning only said that iOS 13 would become mandatory “later this year”, without providing a specific enforcement date;
- iOS 11 builds were still being accepted in early September, including the build that was released on September 10;
- the same validation dialog stated that iOS 15 would become mandatory only in Spring 2027;
- the upload now fails completely before the build reaches App Store Connect or TestFlight.
Because validation fails during upload, we cannot submit this build to App Review or request an expedited review. We have already completed a final bug-fix release for our existing legacy iOS users. Our intention is not to continue supporting iOS 11 indefinitely. We plan to increase the minimum supported iOS version after this release. We are only trying to deliver one final bug-fix update to users who already have the application installed on legacy iOS versions. The fix is ready, but affected production users currently have no way to receive it. I opened Apple Developer Support Case ID 102966589079 on September 17, 2026 and sent a follow-up on September 21. So far I have only received automated acknowledgements. The Developer Support case history also shows: “Email with Apple Developer Support — September 19, 2026” but I did not receive any email from Apple on that date. I checked Inbox, Spam/Junk, and Trash. Phone support for this case currently shows: “Phone support is currently unavailable due to high call volumes.” I have attached screenshots showing:
- the successful August 28 upload with the iOS 13 / iOS 15 warnings;
- the current Error 90068 rejection;
- the support case history.
Could Apple please clarify:
- On what exact date did the MinimumOSVersion 13 requirement begin being enforced?
- Was this enforcement date announced anywhere before it became a hard upload requirement?
- Is there any supported way to upload one final bug-fix build for existing legacy iOS users?
- Could Case ID 102966589079 please be routed to the appropriate App Store Connect / Distribution team?
Thank you.
Final update — resolved
The issue is now fully resolved for us.
Apple ultimately provisioned one-time legacy iOS upload exceptions for all of the affected applications.
The process was as follows:
- RosDomofon received the first one-time exception and the legacy iOS build with
MinimumOSVersion = 11.0was successfully uploaded. - Apple then provisioned the same exception for four related white-label applications under our DOM-IT Developer Team.
- For the two remaining white-label applications distributed through separate partner Developer Teams, Apple asked us to submit individual Feedback Assistant reports from the teams that own those apps.
- Those two exception requests were eventually approved as well.
The final two applications were:
- Redcom Dom умный домофон — FB25015270
- ТелкоДом — FB25015303
I have now successfully uploaded the previously blocked legacy iOS builds for both applications. Error 90068 no longer occurs.
So, in the end, all of the affected applications were able to upload their final legacy bug-fix builds with MinimumOSVersion = 11.0.
For reference, Apple Developer Support also confirmed during this process that enforcement of the iOS 13 minimum requirement began on September 10, 2026.
The main Developer Support case was:
102966589079
The original Feedback Assistant report was:
FB24879771
The most important takeaway from our case is that although the initial response was that exceptions could not be granted, Apple’s internal team was ultimately able to provision one-time exceptions after reviewing the circumstances.
In our case, these were existing production applications with real legacy iOS users, all affected by the same crash, with the fix already prepared. The purpose of the exception was only to deliver one final bug-fix release before increasing the minimum supported iOS version.
Thank you to Apple Developer Support and the App Store Connect teams for helping us resolve this.