“DTiPhoneSimulatorErrorDomain Code 2”

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.

I had recently received my DUNS number and I enrolled for the apple developer program. I also submitted the relevant documents required by apple developer support and I received a reply that they will get back to me within 2 business days but till now no response. My enrollment ID is ZRAGV28M2R . Kindly help to check and get back on the status or if any other documents are required for verification purposes. Thank you.

We have been waiting for the App Review process to complete for almost 2 weeks already. The review process appears to be completely stalled.

Problem Summary I'm experiencing a persistent invalid-credential error with Apple Sign-In on iOS despite having verified every aspect of the configuration over the past 6 months. The error occurs at the Firebase Authentication level after successfully receiving credentials from Apple. Error Message: Firebase auth error: invalid-credential - Invalid OAuth response from apple.com. Environment Platform: iOS (Flutter app) Firebase Auth: v5.7.0 Sign in with Apple: v6.1.2 Xcode: Latest version with capability enabled iOS Target: 13.0+ Bundle ID: com.harmonics.orakl What Actually Happens ✅ Apple Sign-In popup appears ✅ User can authenticate with Apple ID ✅ Apple returns credentials with identityToken ❌ Firebase rejects with invalid-credential error The error occurs at Firebase level, not Apple level. What I've Tried Created a brand new Apple Key (previous key was 6 months old) Tested with both App ID and Service ID in Firebase Completely reinstalled CocoaPods dependencies Verified nonce handling is correct (hashed t

The MagSafe 3 cable is an amazing piece of engineering, showing charged as green and charging as amber. Please consider that carging, being amber and full or reached charging limit, is green, but for a high end company, you need to make the MagSafe wire more useful. A software MagSafe update, like macOS 26.5 was very noticeable for me, as i have the charging limit set on 80%. A new MagSafe 4 would be a simple MagSafe 3 update, creating MagSafe 4, introducing a yellow colour, to mimic macOS window controls. It is very simple, as both red and green diodes are already in MagSafe 3, light physics tells us that red+green=yellow. All we have to do is turn on both of those LED diodes, and we have yellow. MagSafe 4 should have the following: Amber:0%-50% Yellow:50%-90% Green: 90% + or reached charging limit Pulsing Amber: overheating or critical issue with power cut off Pulsing yellow: slow charger, under 30w for macbook air and under 70w for macbook pro. This should be very simple as its a few lines of code

I have a few view controllers in a large UIKit application that previously started showing content right below the bottom of the top navigation toolbar. When testing the same code on iOS 26, these same views have their content extend under the navigation bar and toolbar. I was able to fix it with: if #available(iOS 26, *, *) { self.edgesForExtendedLayout = [.bottom] } when running on iOS 26. I also fixed one or two places where the main view was anchored to self.view.topAnchor instead of self.view.safeAreaLayoutGuide.topAnchor. Although this seems to work, I wonder if this was an intended change in iOS 26 or just a temporary bug in the beta that will be resolved. Were changes made to the safe area and edgesForExtendedLayout logic in iOS 26? If so, is there a place I can see what the specific changes were, so I know my code is handling it properly? Thanks!

Hi everyone, I’m currently using the RoomPlan API, which has been working reliably until recently. However, I’ve started encountering an intermittent error and I’m trying to understand what might be causing it. The error is triggered in the ARSession observer method: session(_ session: ARSession, didFailWithError error: Error) It has occurred on at least two devices: iPhone 14 Pro iPhone 17 Pro Here’s the full error message: ARSession failed domain=com.apple.arkit.error code=102 desc=Required sensor failed. userInfo=[NSLocalizedFailureReason: A sensor failed to deliver the required input., NSUnderlyingError: Error Domain=AVFoundationErrorDomain Code=-11819 Cannot Complete Action UserInfo={NSLocalizedDescription=Cannot Complete Action, NSLocalizedRecoverySuggestion=Try again later.}, NSLocalizedDescription: Required sensor failed.] This seems to indicate that a required sensor (likely LiDAR or camera) failed to provide input, but I’m not sure what’s causing it or why it happens only

Hello, I'm having a serious problem registering for the Apple Developer Program, and I can't resolve it. I applied over two weeks ago, but I still haven't received an activation email. I've also tried using different credit cards, suspecting there might be a problem with my payment method. The main issues are as follows: My order/registration remains in the processing status, I haven't received an activation email, Apple Developer Program support isn't responding. I've already sent over seven emails to support, but haven't received any response or updates. Has anyone else encountered a similar situation?

Hi, I submitted my Family Controls entitlement requests on April 21 for my iOS app, but I still haven’t received an approval, rejection, or any status update. This is blocking my ability to properly test and move forward with the app, since it depends on the Screen Time / Family Controls APIs. Has anyone had a similar delay recently? Is the recommended next step to file a code-level support request with my Team ID, or should I continue waiting? Thanks.

I'm hoping someone can help me get clarity on my app submission for LinkUp, an iMessage-native group scheduling app. Here's the timeline: • Initial rejection (~1 month ago): Rejected under 4.3(a) for duplicating functionality of other apps • I updated screenshots, app description, and submitted again • For the past 2 weeks the app has been stuck with no meaningful response from App Review • I have called Apple support, submitted messages through the Resolution Center, and filed an App Review Board appeal — but I have received no confirmation email for the appeal and it does not appear on my developer support request page What LinkUp actually does: it lets friend groups coordinate availability entirely inside iMessage. Users send a schedule card as a message bubble, and participants vote on availability directly in the conversation thread — no redirects, no external app required. The heatmap updates in the bubble as people respond. To my knowledge, nothing on the App Store does this.

Posting to document a case that matches a pattern of unresolved reports on this forum (e.g. thread #815203 Brutal Time), with the addition of new evidence: my app is missing from both the App Store search index and the Apple Search Ads campaign-creation index. Setup App: ZenTerm (App ID 6760935103, Bundle ID com.zenterm.mobile) Developer: Individual (Japan) Released: 2026-03-31 (live for 45 days) Status: Ready for Sale, 1.3.2 live (released 2026-05-06) App name: pure ASCII, coined word, no other apps share the name Symptoms Channel Result App Store app, search zenterm (exact name) Zero results, 38 days running iTunes Search API (https://itunes.apple.com/search?term=zenterm&country=jp) Returns my app correctly Direct App Store URL Opens product page normally Apple Search Ads — search by app name Zero candidates Apple Search Ads — paste canonical App Store URL Zero candidates The absence from both the App Store search index and the Apple Search Ads selection index is the key new finding. Since these run on