Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

Hello @stopthatnoise Can you share that new project with me to investigate? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. If this is a bug, you can file a bug report here and attach the project there, and I will escalate as needed. Feel free to file now and reply with the FB number in this thread, so we can get a head start on the investigation.  Travis Trotto - DTS Engineer

Even in Xcode 26.3 (Xcode 26.3 Release Candidate Apple silicon.xip) from 2026/Feb/03 the DDI Files for ios 26.x are still missing. No one can work for weeks now. Well done.

I've been experiencing the same problem for two weeks. The support team is inadequate and responds very slowly. I've tried everything; I've re-tried the certificates, the users, the build, everything, but it didn't work.

[quote='875131022, IHadToChooseAUserNameAndIdidntWantTo, /thread/809959?answerId=875131022#875131022, /profile/IHadToChooseAUserNameAndIdidntWantTo'] Are there public APIs to assess notarization? [/quote] That’s tricky, because it depends on your definition of API. The codesign tool has a --check-notarization operation that does that. See Testing a Notarised Product and the codesign man page. While that’s documented, I’m not a fan of using command-line tools as APIs. The code signing requirement language has the notarized constraint. That’s not documented where it should be but it’s debatable whether that’s just because the parent document is stuck in the Documentation Archive. Annoyingly, an equivalent constraint has not been added to the LightweightCodeRequirements framework. If you think that’d be useful, I encourage you to file an enhancement request for it. And if you do, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple

I wanted to shared a quick update on FB21858319. I figured you’d appreciate that given all the work you put in to help isolate it (-: My experience is that Apple is pretty good about fixing local network privacy problems like this one. The critical factor is reproducing the problem, which is why I’ve been so happy to get your cooperation here on this thread. Based on our preliminary analysis of your bug, we think we know what’s going on here. I’m going to offer a little insight into that below, but first I want to set some expectations. Understanding the problem isn’t the same as fixing it. I can’t offer any concrete timeline as to when a fix for this problem will be released. However, when we start seeding a beta release that contains the fix, you should be notified via Feedback Assistant [1]. As to what’s actually happening here, lemme explain a bit about how local network privacy works. As described in TN3179, the local network privacy state on macOS is per user. However, macOS’s networking stack is global

I’m glad to hear that you’re making progress. [quote='875219022, lilan, /thread/773414?answerId=875219022#875219022, /profile/lilan'] We still have to do a submission for NEURLFilter right? [/quote] Yes. Specifically, there’s a process for onboarding with the Oblivious HTTP relay. You can find a link to the submission form at the bottom of How to onboard with an Oblivious HTTP relay hosted by Apple. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I have a standard spiel about this which I’ve included at the end of this reply. Please read it through first. With that in mind, let’s come back to your specific questions: [quote='814841021, Jackson_Hsieh, /thread/814841, /profile/Jackson_Hsieh'] Is it expected behavior for notarization submissions to remain in “In Progress” for such a long period without logs? [/quote] Yes, assuming you’ve hit the “in-depth analysis” path. [quote='814841021, Jackson_Hsieh, /thread/814841, /profile/Jackson_Hsieh'] Is client-side timeout and re-submission the recommended handling for CI workflows? [/quote] I see two common patterns reported here on the forums: Developers hit this on their first notarisation attempt, or otherwise very early in their Mac development ‘journey’. Developers have been happily notarising for a while and then suddenly bump into this. In the first case my advice is to simply wait. That’s the focus of the boilerplate text that I included at the end of this reply. My understanding is that you fall into

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Until which iOS version will Apple continue to support NEHotspotHelper?Is there an official deprecation schedule or timeline?