Apple Maps Guides

What about this poupup when Age Ratings is edited: It would be great if an Apple employee could explain this step by step and clear up any doubts we have about it. Make not sense submitting a new binary to update the Age Ratings form.

You will need to zoom in to see this attachment . I answered this in the Apple Support Communities earlier today . Follow the path to Manage App information .

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

I just found that creating the new version and editing the ratings made the warnings at the top of the screen go away. No Apple employee on here has offered the actual steps, specific information, or answers to any of our questions, so everyone here is just doing trial and error. If what I've done is wrong, then it's Apple's fault in two ways: They didn't explain this process correctly at all; The App Store Connect website removed the warnings when I made those new versions, so Apple's developers wrote it to do that. App Store Connect Engineer said this (it's the accepted answer): You'll be able to update your app's age ratings when you submit a new version of your app. New version, not new binary.

@darkpaw Interesting. Could you share where you found that it’s not necessary to submit a new version or upload a new binary? I’m asking because if that’s the case, it changes things a lot compared to the usual process. Do you know if this comes from an official Apple source or from another site? If you have a link, that would be great. Thanks!

I am tracking some other issues related to localStorage. Please consider filing a bug report. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

Hey there @Apple Staff, the many unnecessary insults here are really embarrassing. However, the underlying frustration seems to be a symptom of the desire to have this feature working on iOS. The lack of it feels like a bug due to the comparison with Android. So, how were the testing results for 17.2? When is this going to be rolled out?

@mattn Go to App Store Connect. Click Apps to see the screen with all your apps' icons. Click one of them. At the top left, there's a white plus button in a blue circle. Click that. Give a new version number. If you're on 2.0.5, enter 2.0.6. Close that dialog. You have created a new release. Click App Information on the left-hand side. The button by Age Ratings that used to say View will now be Edit. Click Edit. Make your selections and confirm the dialog. That's all you have to do, but you have to do it for all of your apps.You do not have to submit the new version, and you do not have to add a new binary. I can't see that your question needs an answer now since the steps you have to go through to fix this issue are actually quite easy. Apple made this a completely stupid process. Their emails were written horribly, and just created confusion. Well done, Apple... ¯_(ツ)_/¯

The crash issue that @edorphy reported in FB21121092 is resolved when you build the app with the released Xcode 26.2 version that came out today, build number 17C52. This version is not the same build as the Xcode 16.2 Release Candidate, so make sure to update to the final release version. @edorphy, had a follow-up statement to me for a different but related issue: you or others may have already seen this one but just in case you haven't: FB21240249 - DeclaredAgeRange: DeclaredAgeRangeAction symbol unavailable on macOS catalyst apps causing crash - documentation says otherwise I appreciate that! I personally had not seen this report, though others within Apple have. We're looking in to it. — Ed Ford,  DTS Engineer

Thank you for the suggestion. I am trying to avoid a chargeback for now, as I still want my Developer Program membership to be activated rather than refunded. I hope Apple Support can manually resolve this issue.

Even with the new Xcode (not release candidate), I get error when uploading from Xcode: Validation Failed: This bundle is invalid. Apple is not currently accepting applications built with this version of Xcode. This is with Xcode 26.2 which has Released December 12, 2025 and Build 17C52. Also, the file name is Xcode_26.2_Apple_silicon.xip.

Well, I'am having the same issue with our SaaS system. We already have a SaaS running on web and Android and we require user login so they can access their data and Apple is rejecting the app. I think we will have to surrender and create a Guest login button that will delete all data on user logout. I don't think this makes sense in a SaaS platform, but I suppose this is the only way to go.

This screenshot is with the Xcode 26.2 (175C2), which supersedes the RC version and was downloaded from the Apple Developer website directly. Not showing at the time of writing on the App Store and seemingly its builds are not accepted (yet).