Apple Maps Guides

Thank you for your post. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.

Apple now accepting Xcode 26.2 RC submissions

As with all of apple's tooling, it'll take between 5-10 years to mature enough to be of any use. Check back around that timeframe.

has now been several more days, and my enrollment status is still Pending with “Purchase your membership” showing on the Developer Account page. I have not received any communication from Apple Support yet, even though my payment was completed and the transaction has fully posted. I also submitted a follow-up to my support case (ID: 102769533427) but still no response. At this point, I am concerned that something may be stuck on Apple’s side and that the enrollment will not complete without manual intervention. If any Apple staff is able to review this issue, I would greatly appreciate assistance. Thank you.

First up, please understand that I’m not claiming that local network privacy (LNP) is bug free. I’ve seen enough reports like this to understand that there are real issues in play, especially on the Mac where the platform’s greater flexibility makes LNP’s job much harder. However, my experience is that it’s difficult for LNP bugs to get traction unless they come with strong evidence, and ideally a reliable set of steps to reproduce. And that’s going to be the focus of my response here. It also means I’m gonna start with the first pathology, primarily so that I can be sure that we’re aligned when it comes to testing. You wrote: On a clean install of macOS Tahoe (our test setup used macOS 26.0.1 on a Mac mini M2 8GB), we upload the app (version 5.1). We run the app, make sure the selected NIC is the proper one, and open the multicast socket. The app asks us to allow Local Network, we allow it. The first divergence I see is at this step. I don’t have your accessory on my network so no local traffic is generated,

By the way, I've tested the QLPreviewView and It's also affected by the same issue! So instead of using QLPreviewPanel, we could generate the thumbnail with QLThumbnailGenerator and then display the result in our app? It seems a lot of work for something Apple should fix 😅

[quote='868778022, JianbinWu, /thread/808040?answerId=868778022#868778022, /profile/JianbinWu'] How to distinguish between those … and the real ethernet adapter which insert on my iPad? [/quote] Unfortunately I can’t see a good way to do that on iOS [1]. I think you could make a reasonable case that those additional interfaces should not be returning IFRTYPE_FUNCTIONAL_WIRED, but instead something more indicative of their purpose (like IFRTYPE_FUNCTIONAL_INTCOPROC). If you’d like to see that change, I encourage you to file a bug along those lines. And if you do file a bug, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] On macOS you have a lot more options, including both System Configuration framework and I/O Kit. Neither of those are API on iOS or its child platforms.

[quote='868809022, Mathias_, /thread/808401?answerId=868809022#868809022, /profile/Mathias_'] just fire off the request blindly and wait to see what happens? [/quote] Yes. And use an expiration handler to deal with the case where the network is super slow. That last bit is critical, because it crops up in practice. In most cases an immediate network request — that is, one without waitsForConnectivity set — will finish promptly. It’ll either succeed or it’ll fail immediately. But there are networks out there in the real world where such requests take a long time. Sometimes that’s caused by bad network conditions. The network is moving packets just fast enough to convince iOS to use it, but not fast enough to get anything useful done. But in other cases it’s caused by weird network configurations. For example, a Wi-Fi accessory might publish a network that goes out of its way to convince iOS that it has a path to the wider Internet when it actually doesn’t. Now, unless you have access to such a network then tes