In situations like this I recommend that you create a new test project from the most appropriate built-in template — in this case that’d likely be iOS > App — and look at how Xcode set things up by default. I did that here in my office and this is what I saw:
<key>MinimumOSVersion</key>
<string>16.0</string>
This was with Xcode 15.0, after changing the project’s iOS Deployment Target to 16.0. This is certainly what App Store Connect is looking for.
Note that I’m looking at the built binary here, not the Info.plist
in the source code because it’s the built binary that matters when it comes to App Store Connect validation.
Try this:
-
In Xcode organiser, select the archive that’s failing.
-
Control click on it and choose Show in Finder.
-
Navigate into the Xcode archive and select your app.
-
Control click on it and choose Show Package Contents.
-
Navigate to your Info.plist
.
-
Open that in a text editor.
What do you see?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"