“DTiPhoneSimulatorErrorDomain Code 2”

[quote='826119021, acabezasg, /thread/826119, /profile/acabezasg'] I have read the other recent stuck In Progress threads from new Developer IDs [/quote] You’ve probably seen my standard response to this, but I’ve included it below just in case other folks stumble across this thread. [quote='826119021, acabezasg, /thread/826119, /profile/acabezasg'] Could the queue be unblocked [/quote] The queue is not blocked. (When something actually goes wrong with notary, the forums light up like a Christmas tree.) [quote='826119021, acabezasg, /thread/826119, /profile/acabezasg'] or is there a team-side configuration that needs flipping? [/quote] It’s not that simple. I can’t offer detailed insight into the “in-depth analysis” case, but my experience, based on talking with many developers here on the forums, is that it usually clears in a day or two. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com You can expect that most uploads will be notar

DevForums is primarily focused on Apple APIs and tools, so I can’t offer specific help with this issue. It’s possible that another third-party developer has seen this before and can help you. If not, I recommend that you seek help via the support channel for the library you’re using. However, I can address this: [quote='826107021, szigetics_nt, /thread/826107, /profile/szigetics_nt'] The problem seems to be that such keychain access groups access cannot be configured for Developer ID signed applications. [/quote] There’s a bunch to unpack here. First up, macOS has multiple keychain implementations. For the details, see TN3137 On Mac keychain APIs and implementations. Keychain access groups imply that you’re using the data protection keychain. Second, the data protection keychain is available to directly distributed programs that use Developer ID signing. See the intersection of the Keychain Sharing row and the Developer ID column in the table in Developer Account Help > Reference > Supported capabilitie

In the same way, @IBDesignable, @IBInspectable have disappeared some time ago. Is it only with objC code or Swift as well ? I do hope I'm wrong, but sometimes, looks like they are silently killing IB to force developers to SwiftUI. That would be very very negative evolution.

Same issue here, pending for over 2 weeks, so sad :((

Are you seeing this with the latest versions of iOS? So iOS 26.4.2 or the iOS 26.5 beta? We tried with different iOS versions & here is our observation. till iOS 26.3 -Pairing setup & DP establishment fails iOS 26.4 & above -Pairing setup works, DP esatablishment fails when iphone act as Subscriber. We need clarifications for below. 1.If the first service is intended only for Pairing setup, when do we need to go for DP establishment and then disconnection? 2.Once data path is established how is the negotiation on what type of service and on which port data needs to be exchanged. 3.Is a separate platform specific service (in our case linux) implementation required to exchange data once NDP is established with the 2nd service. Thanks, Sangeetha.G

We have updated the app to StoreKit 2 and submitted it to the App Store. It's already been approved, and everything is working perfectly with real users. Regarding the other app, the user who experienced problems reported that restarting their iPhone resolved the issue and restored all in-app purchases. It seems the problem is solved for us.

Thanks for the detailed explanation. I checked the Signing & Capabilities settings and enabled Automatically manage signing with my Apple Developer account selected. I’ll also inspect the Frameworks, Libraries, and Embedded Content section to make sure the third-party frameworks are set correctly. I’m going to paste the full console warnings/errors below so it’s easier to identify which framework is causing the issue. Domain: LaunchExecutableValidationErrorDomain Code: 1 Recovery Suggestion: Sign the executable with a valid certificate and provisioning profile. User Info: { DVTErrorCreationDateKey = 2026-05-13 02:48:15 +0000; IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; } -- Unable to Install “PaperHub” Domain: MIInstallerErrorDomain Code: 13 Recovery Suggestion: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.FNhy2z/extracted/IGCSEPastPapers.app : 0xe800801c (No code signature found.) -- Failed to ins

Today is Day 24. Still nothing. All work at my company has now stopped due to this bottleneck. Every day is filled with anxiety and worry over this specific issue. I can't believe Apple does this to their developers after charging them a developer fee. Apple Developer Support - please help. After 24 days, my request to remove the status code 7000 block has ended up in a black hole from which no updates or resolution seems to be provided. I formed an LLC to make & distribute mac apps, only to run right into a brick wall from which no resolution is being provided. This is dream-crushing.

Update — root cause found and a working workaround I cracked it. Posting the solution here so other admins can stop trying random bundle IDs. Root cause (confirmed via watchOS sysdiagnose) When you install a profile with com.apple.applicationaccess + allowListedAppBundleIDs, lsd on the paired Apple Watch immediately sends uninstalledNotifications for every PluginKit extension whose bundle ID is NOT in the whitelist. The watch's Carousel then cascades by terminating the parent apps that own those extensions, disguising the action as user initiated quit. Captured from watchOS sysdiagnose at the moment of profile install: 17:22:56 lsd: Sending uninstalledNotifications for ( pluginID=com.apple.MobileSMS.MessagesAssistantExtension pluginID=com.apple.tincan.SiriExtension pluginID=com.apple.SessionTrackerApp.SessionTrackerSiriExtension ) 17:23:13 Carousel: com.apple.MobileSMS: terminateApplication - uninstalling app (user initiated quit) 17:23:13 Carousel: com.apple.tincan: terminateApplication - uninstalling app (u