“DTiPhoneSimulatorErrorDomain Code 2”

Hello, Adding our case to the long-running thread on this issue (https://developer.apple.com/forums/thread/118465). Our team is the latest to be hit by statusCode 7000 Team is not yet configured for notarization, and we'd like to (a) document the data points in case it helps Apple correlate cases and (b) ask the community whether anyone has seen a faster resolution path than what's been reported here over the past 6 years. Our situation Team ID: A92X4FJ5HU Last successful notarization: 2026-05-18 11:23:26 UTC First rejection: 2026-05-18 17:19:15 UTC (~6 hours later, no apparent trigger on our side) Total rejections since: 22 submissions across 9 days, 100% rejected with statusCode 7000 Open support case: 102900780153 What we have already verified Apple Developer Program membership Active (Renewal Sept 17, 2026) Apple Developer Program License Agreement: Accepted Apr 15, 2026 Free Apps Agreement: Active (Apr 15, 2026 — Sept 16, 2026) Paid Apps Agreement: Active (Mar 17, 2026 — Sept 16, 2026) Banking and tax in

Notarization has been rejecting every submission with statusCode 7000 (Team is not yet configured for notarization) for over five weeks. I'd appreciate any Apple staff who can confirm the gate status or re-route this internally. Account: Team ID: ZLPP2G8NG3 Account type: Individual, ACTIVE membership Region: EU (Czech Republic) The submission is technically clean — this is rejected at the gate, not on content: Developer ID Application cert valid (expires 2031), full WWDR chain Signed with hardened runtime + secure timestamp codesign --verify --deep --strict passes notarytool uploads succeed, then Rejected in ~30-60s log shows issues: null (the archive is never opened) Confirmed it is NOT app-specific: a 50 KB hello-world C binary, signed the same way, is rejected identically. Latest canary submission: 95833847-e70f-41fe-b61f-c9dc9ffd90ed (2026-05-27) -> 7000 Timeline: 2026-04-20 first 7000 rejection (app, after ~60h In Progress) 2026-04-29 escalated to engineering (case 102873818441, advisor Ronan) 2026-05

We are currently experiencing a critical issue with our Apple Developer account related to production certificates for live customers using Apple Pay. Each customer integration requires a minimum of two certificates. At present, our account has reached 20 certificates, and we are facing limitations that impact our ability to onboard new customers. Recently, deletion of certain certificates caused a major outage, resulting in service disruption for live customers. This outage has had significant financial implications, This may be held liable for the revenue lost. We urgently request clarification on the following: What are the official license limit restrictions for production certificates on Apple Developer accounts? Is there a way to extend or increase the certificate limit to support multiple live customer integrations? What best practices should we follow to avoid outages when managing certificates for Apple Pay? Given the severity of this issue, we kindly ask for immediate guidance and support t

Hello everyone, We are in the process of migrating a high-performance storage KEXT to DriverKit. During our initial validation phase, we noticed a performance gap between the DEXT and the KEXT, which prompted us to try and optimize our I/O handling process. Background and Motivation: Our test hardware is a RAID 0 array of two HDDs. According to AJA System Test, our legacy KEXT achieves a write speed of about 645 MB/s on this hardware, whereas the new DEXT reaches about 565 MB/s. We suspect the primary reason for this performance gap might be that the DEXT, by default, uses a serial work-loop to submit I/O commands, which fails to fully leverage the parallelism of the hardware array. Therefore, to eliminate this bottleneck and improve performance, we configured a dedicated parallel dispatch queue (MyParallelIOQueue) for the UserProcessParallelTask method. However, during our implementation attempt, we encountered a critical issue that caused a system-wide crash. The Operation Causing the Panic: We con

There are many situations where debug breaking points are not the right tool. What I often need is a log that shows what gets called, with how much frequency, and in which order. There are so many times where I have to add print statements, re compile, re run, see that I didn't include all the print statements I needed, and repeat a couple of times. My proposal (with zero knowledge of technical feasibility), is that much like we have break points, add print break points for logging without modifying code. It would be nice too, if I could also, add a timer break point, where I can tag a function definition, and every time it gets called, it's are timed. Again, no idea if this is possible, but it would be extremely helpful for me, and I'm guessing to many other devs as well. Thoughts?

Hello Albert! I am experiencing some strange bugs around DeviceActivityEvents (part of the DeviceActivity framework) on iOS 26 / iOS 26.1 / iOS 26.2 beta: When creating a DeviceActivityEvent we can assign a threshold and applicationTokens. The idea is, that after the user has spent said threshold on said apps, eventDidReachThreshold() is called. The property includesPastActivity is set to false. On iOS 26 however, it happens (quite reliably after updating to a new beta seed) quite often that eventDidReachThreshold() is called immediately (after a couple of seconds) instead of waiting for the threshold to be met. Is anyone else seeing similar issues on iOS 26 / iOS 26.1 / iOS 26.2 beta? Only workaround I have found is to ask users to revoke and re-grant Screen Time permissions. This only holds for about two weeks though or at most until the next iOS 26 beta update is installed, so it is not a permanent solution unfortunately. Feedback (incl. sysdiagnoses and sample project) is filed under: FB18061981

Currently we are building a service based on Fairplay SDK version 26.0. Currently our solution is using version 4.5.4. When we run the below request to get version we get proper response curl http://xx.xx.xx.xx:8080/fps/v Response - V26.0 Our client applications call below two APIs https://GW_HOST:8080/fairplay_cert https://GW_HOST:8080/fairplay_license Within the cert API call, we are returning the fairplay public certificate. Currently we are trying to use the test certificate provided along with Fairplay SDK (test_fps_certificate_v26.bin) Then within the fairplay_license API call, we are trying to reach fairplay service based on Fairplay SDK v26 We are seeing some issues with below request(attaching the request json payload) curl -v -X POST -H Content-Type: application/json -d @SDKValidation.json http://xx.xx.xx.xx:8080/fps SDKValidation.json We are getting Empty response from server When we checked the apache error logs in the file /etc/httpd/logs/error_log we see some exception. We are sharin

Hi, we have developed an application that streams data from two BLE peripherals at a rate of 14.5kbps per peripheral. Until now, our devices streamed in near real time with no lag on all Apple devices with Bluetooth 5.0 or greater. Since the release of the iPhone 17 series and the iPad A16, we have reports from users of the data being streamed at significantly lower rates than expected. Any help here would be greatly appreciated as our customers are being affected by this change.

We have an Apple Watch app and companion iPhone app that we distribute via Enterprise Distribution using OTA manual installation. (We are on an Apple Enterprise Developer Team) With WatchOS 26.4 and earlier, the app would install fine on both the phone and the watch. However, after updating to WatchOS 26.5 (and iOS 26.5), the app will not install on the watch. It will install on the phone and we can trust the developer/run the phone app. However, when we go into the Apple Watch app on the phone and choose Install for the app, it tries to install for a minute and then returns an error The app could not be installed at this time. We have tried the following remedies: Restarting both watch and phone, and reinstalling the app on phone Factory resetting both the watch and the phone, then reinstalling app Generating a new Distribution Certificate and new manual profiles for the app in Apple Developer Looking through console logs from both the phone and the watch Confirmed that we can install other (non-Enterprise)

To the App Review and Developer Support Teams, I am writing this post to bring an ongoing and critical issue to your attention, as standard support channels have failed to provide any resolution or clear communication. Issue Summary: My application’s last two versions have been successfully reviewed and approved. However, three In-App Purchases remain stuck in the review process. Lack of Communication: I have opened several support cases regarding this delay, yet I have received no response or actionable feedback. The lack of synchronization between the App Review and Support teams is causing significant operational disruptions. The current communication gap and the slow response times are directly impacting my business and user experience. Impact: It is unacceptable to have a live application with Pending monetization features for such an extended period. This delay is causing financial loss and preventing my users from accessing the services they need. Request: I request an immediate update on the