Apple Maps Guides

There have been some behavioral changes on N1 chip devices; especially in areas where the BT spec has not had a single way of interpreting things. We have been observing these changes and changing them back if appropriate and are considered regressions. So, the first thing you should do is to test all this in the latest iOS 26.3 and see if anything has changed from your earlier observations. Also, there would have been some changes on patterns of use that were never meant to work, but just happened to work, and those would have been corrected. For example, scanning without services is not supposed to work, and was never expected to work in the background. If you are scanning in the background without services, and whatever the Flutter library may have been doing to work around that limitation (if anything), and that has stopped working, you can consider that a bug that has been fixed. Similarly, advertising packets in the background have always been on a best effort basis. Also, it has always been possible th

Whether iOS provides any mechanism or API that allows iPhone apps to trigger or request parental re-approval after the application has already been installed PermissionKit has that for you: https://developer.apple.com/documentation/PermissionKit/SignificantAppUpdateTopic Also from which iOS version this capabilities will work & how to handle lower iOS version which is not supporting. The APIs seem to only be supported in iOS 26.2 and above. The laws say that A developer shall verify through the app store's data sharing methods.... Since Apple has not provided any data sharing method for users on iOS versions before 26.2, my interpretation is that we do not need to do any age verification for users on older versions of iOS, but I can not be sure at this time and this is not legal advice. I doubt Apple will provide any recommendation since doing that could be considered legal advice. The only way we will know for sure though is for the deadlines to pass, a law to come into effect, a releva

If your app has been rejected and you need help resolving the issue, consider taking advantage of one of the following support options available from App Review: Reply to the message from App Review in App Store Connect and request clarification. Request a call with an Apple representative to discuss the outcome of the review. Submit an appeal to the App Review Board if you believe your app follows the App Review Guidelines. Visit the Contact Us page on Apple Developer and select the App Review tile to learn more.

I tested the reproduction I cobbled together again this morning with the current Xcode 26.4 beta and it no longer displayed the issue. Xcode version details: Apple Swift version 6.3 (swiftlang-6.3.0.119.2 clang-2100.0.119.1) Target: arm64-apple-macosx26.0 If it's possible to provide positive confirmation that the underlying issue was identified and resolved that'd be great, but even if not thanks to whoever worked on this!

Also running Into the same issue. Apple is not clear exactly on what needs to be done as I’ve followed the guides and disclosed as I should but still got rejected.

Hi, I am in a similar position as you and wondering the same thing! Have you received any response from Apple's end regarding your eligibility? Thanks!

We have the same sutiation. More than week ago submitted 2 apps, and it's still stuck on In Review status with zero updates. No updates in statuses. No updates from email support Apple Team. We create some tickets on support tab, but no updates from Apple Team. Apple’s review process usually isn’t this slow, so I’m starting to wonder if something’s broken on their end… Would appreciate any insights or updates from others who’ve managed to get through this too!!!

Hi there, this is what AI just told me because I thought our MDM is blocking the process and I specifically asked AI about it again. Let your MDM know about this: **PSA: iOS 18.5 Simulator Issues with Defender/Cisco AnyConnect - Architecture Change** If you're experiencing issues with iOS 18.5 simulators failing to launch while iOS 18.2 and earlier simulators work fine, this may be due to a fundamental architecture change Apple introduced: **What Changed:** Apple changed the simulator architecture in iOS 18.5 (and macOS 15.x): **iOS 18.2 and earlier:** - Simulator ran as a single process - launchd_sim was a simple subprocess - Minimal network communication - ✅ Works with security software like Defender/AnyConnect **iOS 18.5+ (and iPhone 17.x simulators):** - New Virtualization Framework integration - Simulator now uses multiple isolated processes - launchd_sim binds to virtual network interfaces (vmnet) - Attempts to bind to 127.0.0.1:XXXX for localhost communication between processes - Requ

Can you re-test on the just-seeded 26.4b1 release? There’s a similar issue (FB21376045) called out in the macOS Tahoe 26.4 Beta Release Notes notes. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I asked about this internally and the answer is that the machinery used by Platform SSO isn’t something available to third-party developers (other than via Platform SSO itself, of course). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You should probably raise these as bugs in the usual way. They won't really get progressed if they're only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others (especially Apple employees) can link to them.