“DTiPhoneSimulatorErrorDomain Code 2”

Hi everyone, I'm hoping to hear from developers who have submitted Live Caller ID Lookup entitlement requests, especially anyone successfully onboarded after the PIR architecture became required. My own request (ID 2C4HJDWYJ6, submitted March 23, 2026) has been under review for 85 days. Apple Developer Support confirmed on May 8 that it's in the pipeline to be onboarded but I haven't received a concrete timeline. Infrastructure is fully deployed and verified per Apple's PIR documentation: OHTTP Gateway: https://gateway.zinfo.ge PIR Service: https://service.zinfo.ge (Apple's Swift PIR Service) Token Issuer: https://issuer.zinfo.ge DNS TXT record correctly configured HTTP/2, TLS, Protocol Buffers wire format Production database loaded Questions for the community: For developers already onboarded, how long did your review take from final submission to approval? Did the Live Caller ID Lookup capability appear automatically in Certificates, Identifiers & Profiles after approval, or was there an additi

Hi everyone, I'm an independent developer facing a critical and frustrating App Review delay. I've exhausted standard channels without a real resolution and am turning to the community for advice from anyone who may have experienced something similar. 1. The Problem My app, Trainer Schedule & Booking, was submitted for review on May 7, 2026. As of today (May 20), its status remains Waiting for Review — over 12 days and counting. Apple ID: 6766453138 Submission ID: ea4a779c-7e1d-4def-8a95-c252afdbf618 2. Context & Steps Taken Account History: I acknowledge that my account has a past record. Earlier submissions were rejected under Guidelines 4.3 (Design Spam) and 3.1.2 (Subscriptions). I have conducted a thorough review, permanently removed all non-compliant apps from sale, and am committed to full compliance moving forward. The Current App: This is a completely new, vertically-focused tool for coach/student scheduling, developed independently over several months. I have verified its compliance

I'm attempting to create a feature where I can allow two levels of information

with the latest updates on two of our iPhones run running 26.4 and the other 26.5 developed beta we have lost the ability to use CarPlay functionality via the Apple certified cable. Both phone showed the phone is connected and it is charging however functionality are greyed out on display in the 2022 Nissan rogue. Bluetooth still function properly as you could send and receive calls. However, functionality via the cable does not work. You cannot play music either. this feature also greyed. A trip to the Nissan dealer for more troubleshooting provided the following. A version 15 iPhone Connect via usb-c cable and functioned properly. As well as an android device. But again, hook up two iPhones one with version 26.5 DB and the other 26.4 both iPhone 14 would not work. After we left the dealership, I had a hunch that the issue with the latest update that both of these phones received over last week. I came home and connected an iPhone 6S which has a much older software version and it connected

I'm trying to update the iCloud data handling in our app, and I'm running into an issue with a particular file on one particular device. This file never downloads & I haven't been able to pinpoint what's off about it. Right now we just have 2 iCloud accounts & a handful of devices, so I haven't been able to narrow it down yet, but in most cases, all the cloud files download as expected. However, whether or not the file eventually downloads, the NSURLUbiquitousItemDownloadRequestedKey key seems to be completely useless. For the following code: NSError *error = nil; BOOL success = [[NSFileManager defaultManager] startDownloadingUbiquitousItemAtURL:self.fileURL error:&error]; if (!success) { NSLog(@error downloading %@ : %@, self.fileURL, error); } else { NSDictionary *resourceValues = [self.fileURL resourceValuesForKeys:@[NSURLUbiquitousItemDownloadRequestedKey, NSURLUbiquitousItemIsDownloadingKey, NSURLUbiquitousItemDownloadingErrorKey, NSURLUbiquitousItemDownloadingStatusKey] err

Hello, I'm posting again — and unfortunately, I already know how this thread is going to go. My app (ID: 6756186616) has now been stuck in In Review for 80 days. To save everyone time, here is the reply I expect to receive within a day or two, copy-pasted from the response on my last thread: Thank you for your post. We're investigating and The App Review team will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us. Nothing actually happened after that reply last time. No follow-up in App Store Connect. No further communication. Just silence. When I escalated to Developer Support (case #20000111565861), I was told explicitly that Developer Support has no way to reach the App Review team and no authority to intervene on submissions stuck in review. So Developer Support points back to App Review, and the standard forum reply points back to contact us — which loops back to Developer Support. This is a closed loop that does

Over the last two weeks, I’ve had sporadic reports from users who suddenly have a corrupt image in the database for my app. It’s only affecting a few users and may possibly have been fixed with iOS 26.4.1 (I’m not sure). In any case, this started suddenly with the release of iOS 26.4 - our app has not been changed in several months. But I wanted to share what’s happening in case others are experiencing this. My app lets users import photos from the camera roll, photo albums, etc. Once the user has selected an image, the app saves this to a SQLite3 database using “image.heicData()”. For the four or five users who have been affected by this problem, the heicData call returns successfully, with a non-nil Data value. But the image itself is corrupt and unreadable. When the user tries to later open a screen containing the image, the app crashes. I’ve had to manually guide each user through tracking down and removing the affected item or items to resolve it, which is a bad experience for them and time-cons

Hi, hoping for guidance on what's a long-running bug for our app. The problem We have a transcription app on iPhone 17 Pro Max running iOS 26.5. Recording flow uses AVAudioEngine.installTap(onBus:) to capture PCM into a JS bridge for streaming to a remote transcription service. A parallel AVAudioRecorder writes the same audio to disk as backup. When the user starts a recording and locks the phone, iOS terminates our process with SIGKILL at approximately 50 seconds of continuous background time, despite: UIBackgroundModes includes audio (verified in shipping IPA's Info.plist) AVAudioSession.setCategory(.playAndRecord, mode: .default) is active AVAudioEngine is running with installTap producing PCM buffers right up to the moment of death UIApplication.backgroundTimeRemaining returns Double.greatestFiniteMagnitude at applicationDidEnterBackground (verified in our event log) No AVAudioSession.interruptionNotification is delivered before the kill. iOS terminates the process cleanly with no warning event to our obs