“DTiPhoneSimulatorErrorDomain Code 2”

@DTS Engineer Hello, we have the same issue and have opened both feedback and another thread, but it's been 2 weeks since. Could somebody from your end please look into this for us? https://developer.apple.com/forums/thread/826094 Thanks

Folks, I’m gonna lock this thread. It’s clear that people are finding the thread and piling on to it, without really grokking my earlier response. That’s not helpful, because the exact evolution of this process varies for each team. So, if you find yourself here: Please read this reply and this reply. My experience is that this “in-depth analysis” usually clears after a few days. If your requests have been stuck in the In Progress state for more than a week, please start a new thread in the Code Signing > Notarization subtopic and I’ll respond there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

AFAIK there’s been no change of policy on this front. That WWDC session, and for that matter TN3134, don’t discuss this debugging affordance because they’re focused on deployment, not development. [quote='827318021, Colin_newbie, /thread/827318, /profile/Colin_newbie'] All I get is NEConfigurationErrorDomain Code=10 permission denied before my app code even runs. [/quote] I don’t understand this comment. This affordance affects your ability to save a configuration. That is, with this affordance your container app can successfully save a configuration using NEFilterManager.saveToPreferences() under circumstances where it would not normally be allowed to do that. So I’m struggling to see how you could get into this situation “before my app code even runs”. Please clarify. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='888791022, RomainDropB, /thread/827228?answerId=888791022#888791022, /profile/RomainDropB'] The url-filter-provider capability does not appear in the Capability Requests tab of my developer portal. [/quote] This isn’t a standalone capability. Rather, this feature is gated by the url-filter-provider element of the com.apple.developer.networking.networkextension entitlement. And that entitlement is available all paid developers. To activate it: In Signing & Capabilities, make sure you have automatic code signing enabled [1] and select a paid team from the Team popu. Click the add (+) capability button and choose Network Extensions. Enable URL Filter. Do this for both your container app target and the URL filter provider target. [quote='888791022, RomainDropB, /thread/827228?answerId=888791022#888791022, /profile/RomainDropB'] does the full PIR server + Privacy Pass infrastructure need to be deployed and running before submitting the form, [/quote] Yes. Part of the approval process checks th

[quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] I can now verity the .pkg file with Transporter and upload to App Store Connect [/quote] Cool. [quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] but installing to the Applications folder does not work. [/quote] Installing how? By opening the .pkg with the Installer? That’s not expected to work. In general, you can’t test distribution signed code like this. Rather, upload your app to the App Store and then test it with TestFlight. For more backstory, see Don’t Run App Store Distribution-Signed Code. [quote='888831022, Paul from Vancouver, /thread/826941?answerId=888831022#888831022, /profile/Paul+from+Vancouver'] I am making an Adobe AIR app so I may need to treat the UNIX executable included in the .app file as an embedded file. [/quote] I’m not sure I understand what you’re getting at here. If you’re publishing

One last thing. Handling different device sizes: Handling Different Screen Sizes (The Dynamic Detective) On a different device (like an iPhone SE or an iPhone Pro Max), or if the user rotates their phone into landscape mode, that secret extra space won't be 228 pixels anymore. It might be 200 pixels, 250 pixels, or something else entirely. If we hardcoded 228 into the app, the keyboard would start glitching again on other screen sizes. To solve this for every single iPhone and iPad size, we made our code act like a detective right before the keyboard slides up. How the Code Automatically Adapts Instead of guessing the number, the code visually inspects iOS's internal blueprint at the very last millisecond (inside viewIsAppearing) and pulls out the exact secret number for that specific device. Here is how the math automatically updates on a different phone where the secret space is, say, 250 pixels: The Investigation: You want a height of 450. The code checks the system blue

I was able to find a fix after 2 intense days troubleshooting this with Claude and GPT. Eventually Gemini solved the problem for me! Sending 2 messages due to 7k char limitation Problem: Custom iOS keyboard extension (UIInputViewController, SwiftUI content via UIHostingController). On every appearance, the keyboard window visibly resizes — the host app's UI reacts to it. Happens in every host app (Instagram, iMessage, etc.), not app-specific. The desired behaviour is what Bitmoji/Wispr do — keyboard just appears cleanly with no visible resize. What the logs show (captured via in-keyboard debug overlay — Xcode console doesn't work for extensions): Every single appearance, without exception, produces this sequence in viewDidLayoutSubviews: viewDidLoad: bounds.height = 0.0 viewDidLayoutSubviews: 844.0 viewDidLayoutSubviews: 844.0 (multiple passes) viewDidLayoutSubviews: 678.0 (multiple passes) viewDidLayoutSubviews: 450.0 ← our target viewDidAppear fires at 678, not 450. The final 678→450 snap

my goal is to prvoide a browser based remote control solution for VZVirtualMahineView. So that user can connect to vms from anywhere. i am almost done with this. I think i have to live with this limitation Every web-based remote desktop solution (VNC web clients, NoMachine web, etc.) has this exact same limitation. the mac os host assigned shortcuts takes precedence over web browser key press event. we cant do anything about this. pressing the fn key with f1, f2, f3 sends key codes correctly. there is no probem with this. if it is reserved by mac os(ex. cmd + space, F11 etc) it takes precedance over browser. we have to live with this limitation. thanks for your help so far.

Hello! Thanks for spending time with with the intelligence features in Xcode. I'm one of the engineers and engineering managers who builds our features in this area, and it's always good to know people are so passionate about this. As we outlined in that original response, the intelligence features in Xcode actually do use a number of features that are exclusive to Macs with Apple Silicon, even when using the coding agent integrations. I'm glad you were able to use a workaround to your problem by installing a different version of the Claude Code binary we use for the agent runtime, but the thing that is really on us here is not warning you far earlier in your journey through the process that Intelligence features on Intel is not a well-supported configuration. Coding agents are very resilient to minor issues, so if a tool call to one of Xcode's tools fails, or something similar goes wrong, you may not even be negatively affected by the fact that this is not a configuration we suppor

I am seeing the problem as well and have been for a couple of months. One of my beta testers mentioned today that Carrot was reporting it so I searched the forums and found this thread. It's reassuring to know that it is a TestFlight issue because I assumed that I had broken something and have been rolling back lots of code trying to work out what it was that I had broken. One thing I have noticed is that it usually happens after the tester has updated watchOS. I had several reports a couple of months ago after watchOS 26.4 was released. And it has been reported more often again since watchOS 26.5 was released. I always ask them to downgrade to an older beta or the App Store version and it always fixes the problem, even if they then upgrade to the latest beta again.