Apple Maps Guides

@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).

Is there a guide for macOS on the steps you describe at the end, that is on how to allocate a swapfile, Just to be clear, you're not actually creating a swapfile as such. Your mapping a file into memory which means, assuming the mapping MAP_SHARED, the VM system will then use that file as the backing store for that memory range. That gives you basically the same behavior as swap backed system memory, but it isn't ACTUALLY the same as using true swap (for example, you'll be writing the data directly back to file, so there won't be any compression or VM level encryption). mmap that swapfile into memory, mmap is a standard Unix API, which means we don't really provide specific documentation for it, however, there is an old code snippet here showing how it works. One note I will note is that some of the recommendations there aren't really relevant anymore, particularly any recommendation about limiting mapping size. Those concerns where driven by the limited 32-bit address spac

The weird thing is, SecKeyCreateRandomKey() does create an entry with the correct ACL where only my program can access the key. In all cases I'm creating the ACL simply like so: SecAccessCreate(label as CFString, nil, &acl) The program should also have a valid code signature, because otherwise macOS doesn't even let it start up. Running from a terminal immediately results in Killed: 9, with the Console program showing an accompanying ASP: Security policy would not allow process, and opening from Finder results in The application “something.app” can’t be opened. And indeed, I do have a Personal Team set in Xcode, it's just not enrolled in the paid developer program. I did also notice that my signed executables actually ran even without updates within a year, so I simply figured that it works because my Personal Team's certificate was still in fact signed by Apple, it just doesn't have access to any restricted entitlements. Since I'm not using those, there's also no provisioning profile to deal wit

If you do not update the ge rating and submit a new version before Jan 31 2025, the next time that you need to update that app it will trigger a significant change which presumably a more difficult review process. This is specified at the end of the email that you received from Apple. Please also note that the Texas SB2420 legislation goes into effect January 1, 2026. Under this law, making an age rating change to apps distributed in Texas would be considered a significant change. If you update your age rating after this date, you may need to trigger the significant change consent process.

Same issue https://developer.apple.com/forums/thread/803714 No reaction from Apple

Are there any examples of Apple designed apps that behave in this manner? I can't seem to find any. If I go to any screen that is asking for my Apple ID Password, there are no buttons or UI allowing for VoiceOver to speak the password. These types of buttons in general to me seem to defeat the purpose of secure text entry.