Search results for

“DTiPhoneSimulatorErrorDomain Code 2”

162,373 results found

Post

Replies

Boosts

Views

Activity

Reply to AlarmKit Fixed Schedule Going off at Midnight

I have refactored my code using your approach @ekurutepe and still get users complaining about the same issue (random or midnight alarms). There are also some people complaining that they uninstalled the app but still receive the alarms.

App & System Services General

Reply to AlarmKit alarm occasionally fires at exactly 12:00 AM

Thanks for details @Hakoniwa . I have refactored my code many times and still get users complaining about the same issue (random or midnight alarms). There are also some people complaining that they uninstalled the app but still receive the alarms.

App & System Services General

Reply to Could not launch app on watchOS downloaded from TestFlight

I've since heard of two other popular apps affected. There aren't all that many Apple Watch apps compared to the number of iPhone apps, and this may only be affecting ones that are set to run independently of their iPhone counterpart (so an even smaller percentage).

App & System Services General

Reply to Issues with TCP Socket Management and Ghost Data on ESP32 (Swift)

[quote='887740022, Gabriel_Heidemann, /thread/826000?answerId=887740022#887740022, /profile/Gabriel_Heidemann'] According to them, these strings are originating from the app. [/quote] To quote House [1], “everybody lies” (-: Fortunately, you don’t have to take their word for it. Fire up an RVI packet trace and look at what the iOS device is actually sending. If you see the gibberish there, you know that you need to dig deeper into your code. If not, you have evidence to take to your hardware team. Oh, and just FYI, if you’re working on a Wi-Fi based accessory, I have a bunch of hints and tips on that front in Extra-ordinary Networking > Working with a Wi-Fi Accessory. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] https://en.wikipedia.org/wiki/House_(TV_series)

App & System Services Networking

Developer Program Enrollment Fails With "Unable to Continue" - Support Case Open for Months Without Resolution

Hello, I am trying to enroll in the Apple Developer Program, but the enrollment process consistently fails inside the official Apple Developer app on macOS. Issue After signing in successfully and clicking “Continue Your Enrollment”, the app immediately shows: “Unable to Continue. Contact support at https://developer.apple.com/contact/” The issue occurs repeatedly for last 4 months and prevents me from completing enrollment entirely. Environment Country: India Enrollment Type: Organisation Device: MacBook macOS Version: macOS 26.4.1 Apple Developer App: Latest available version Apple ID signed in correctly on macOS System Settings What I Already Tried Signed out and signed back into Apple ID Reinstalled the Apple Developer app Restarted the Mac Tried different internet connections Verified payment/account region settings Attempted enrollment multiple times across different days The same error continues. Support Case I contacted Apple Developer Support multiple times over last 4 months and latest , they asked

Developer Tools & Services Apple Developer Program

Reply to 2+ months blocked on error 7000. Apple's "correct escalation path" is broken.

Hey Brad, Since all work at my company has ground to a halt due to the status code 7000 issue, I did some deep-diving on other people's experience with this problem. And to my shock I discovered something: No one has ever posted online that this problem was resolved for them. There's hundreds of posts about Team ID not yet configured for notarization and not a single follow-up success story. Not here, reddit, github communities, etc. We have lots of evidence that many people have encountered this problem, and no evidence that anyone has overcome it. I wrote a thread about it here: https://developer.apple.com/forums/thread/826413

Code Signing Notarization

Mind blown 🤯 Not a single person has EVER posted a follow-up that their Status Code 7000 problem had been resolved. Anywhere - here, reddit, github communities. Not a single success reply.

It's true - go ahead and look. Every single unlucky soul that encounters the status code 7000, Team ID not yet configured for notarization just stops developing for the mac, as they are left with no other option. Based on a deep review of all posts on the subject in multiple online communities & web searches, here's what we know: This problem has existed since at least 2018 People that drew the short straw are directed to contact Apple Developer Support via email Usually after 3 weeks an automated message is sent that the issue has been added to the queue of the relevant team Follow-up calls always indicate that the relevant team cannot be messaged even by Apple Support and that you just have to wait for them to contact you. In the past year, Apple now uses an AI bot to email you periodically to inform you that they are monitoring the situation and will let you know once the relevant team has completed their work. Apple makes it very clear you're trading emails back and forth with an LLM. The rel

Code Signing Notarization

540

Reply to NSInvalidArgumentException while sharing in UIDocumentInteractionController

Thank you for your quick response. Attached 3 decrypted stack traces. Some sensitive data is hidden log_1.txt log_2.txt log_3.txt 2. We are seeing crashes on versions of iOS 26.2 inclusive and above. I assume that it occurs on all versions of iOS 26.x 3. We download the file, check that the url is valid and the file exists. Part of the code is indicated below guard url.isFileURL, url.pathExtension == pdf else { completion(false) return } guard fileManager.fileExists(atPath: url.path) else { completion(false) return } let interactionController = UIDocumentInteractionController(url: url) interactionController.delegate = self let success = interactionController.presentPreview(animated: true) We are seeing this on a small number of users, so far it is not a critical percentage. At the moment, we cannot estimate which part of the attempts to open files is failing and which is successful. We expect technical improvements from APPLE and hope for an early fix.

UI Frameworks UIKit

Reply to Workarounds for Xcode previews errors: Cannot preview in this file - Failed to Launch

I did another test on two different machines seemingly configured in the same way (macOS 26.4.1, Xcode 26.5), and got divergent results. These are the steps I've taken in each case: In System Preferences > Privacy & Security, remove Xcode from Full Disk Access and Files & Folders. Reboot. Open a project under the Documents folder. The user is prompted to grant Xcode access to the Documents folder. If access is denied, Xcode correctly reports that it doesn't have permissions to open the project (Xcode can still create new projects inside Documents, but I assume that this is expected behavior). In System Preferences > Privacy & Security > Files & Folder, grant Xcode access to the Documents folder. Restart Xcode and reopen the same project. The project can now be opened. At this point, in one machine the preview shows up correctly, but in the other machine I get the “Failed to launch” error I've originally posted, and I need to apply one of the workarounds I've originally mentio

Developer Tools & Services Xcode

Please Help, App stuck in "Waiting for Review" for 10+ days with no feedback

Hi Apple Review Team, Our app (Apple ID: [6744090840] has been stuck in Waiting for Review since May 5th — over 10 days now. This version includes critical IAP fixes that are currently causing purchase failures for live users. We've submitted an Expedited Review Request, but the status hasn't changed. Could you confirm if: 1.Additional documentation is needed? 2.There's a technical blocker we should address? We're ready to provide any info or make changes immediately to resolve this.

App Store Distribution & Marketing App Review

161

Reply to StatusCode 7000 "Team is not yet configured for notarization". It's been over five days, no resolution

[quote='885900022, DTS Engineer, /thread/824359?answerId=885900022#885900022'] I [/quote] Quinn….There’s never once been a post by anyone that their status code 7000 problem got resolved. A review of this forum, GitHub communities, and Reddit show nearly a hundred developers get hit with this status block, and all hundred of them never got the block lifted, regardless of length of time. If you get hit with the status code 7000 bug, your time as an app developer is over. Thanks for the developer fee, no refunds.

Code Signing Notarization

First subscription stuck in "Developer Action Needed", no IAP section on version page, reviewer hits "product is not available for purchase" — works fine on my own TestFlight install

I'm preparing my first App Store submission and have hit a chain of issues that appear to be backend state problems I can't resolve from the App Store Connect UI. I've already opened a DTS case but wanted to ask here in case anyone has seen this combination before. Setup: iOS app with first-time subscriptions (auto-renewable, 7-day free trial) Two products: bitcoinhq_pro_monthly and bitcoinhq_pro_annual Both in the same subscription group Bitcoin HQ Pro Paid Apps Agreement is Active Bundle ID, prices (all 175 territories including United States), intro offers (Free for the first week in all territories), localizations all configured Important context: On my own iPad (TestFlight build, signed into my normal sandbox account), the full flow works perfectly — paywall loads on first launch after install, both products show with correct prices, tapping Subscribe opens the StoreKit sheet, purchase completes, the entitlement grants, and Pro features unlock. So the app code and RevenueCat configurati

105

Reply to codesign tool generates "timestamps differ by XXX seconds" error

Thank you Quinn, this is helpful. I just read up the contents of the header file you note and the comments on those fields are clear. So I suspect that the Mac doing the signing has a clock that’s way of sync with reality, so these two values end up significantly different, and thus this problem. I read through the linked TN3161: Inside Code Signing: Certificates | Apple Developer Documentation and it says that it contacts timestamp.apple.com for getting a secure timestamp. Is there a tool that I could use to directly issue a similar request against that server and see what it returns? That might help us debug this on many of these hosts where this happens intermittently. As far as I can see, there's no option/flag in codesign which would allow us to print verbose logs showing it communicating with the timestamp authority server. One other question, that doc also says: Don’t confused the Timestamp and Signed Time fields. The latter is not secured by the Apple timestamp service. Rather, codes

Code Signing General

StoreKit testing not working on iOS26.5 simulator

Hi, I'm trying to run our StoreKit unit tests with Xcode26.5 on an iOS26.5 simulator. Host computer has macOS26.5. All tests are failing and in the console I see logs such as [SKTestSession] Error saving configuration file: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error deleting all transactions: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error clearing overrides: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error setting value to 1 for identifier 2 for jp.unext.mediaplayer: Error Domain=SKInternalErrorDomain Code=3 (null) And the simulator asks me to provide my AppleID. Tests have been broken since at least 26.4 The release notes claims that it has been fixed but not for me. https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-26_5-release-notes#StoreKit-Testing-in-Xcode Does anyone else have the same issue? Reported FB22774836 just in case.

Developer Tools & Services Xcode StoreKit Test StoreKit

497

XCode Quick Help panel

I'm a big fan of keeping documentation in the code, so it appears at the point of use. Obviously, DocC and the Quick Help panel are a pretty important part of that strategy. Unfortunately, it only works randomly, so even if I've just build documentation (which should not even matter, the doc is just a cmd+click away), Quick Help stays blank, often even on system items like Label. It seems totally accidental, which makes it hard to make to reproduce. Sometimes an Xcode restart helps, sometimes not. Sometimes changing the editor display helps, sometimes not. Any tips on that?

Developer Tools & Services Xcode DocC

130