“DTiPhoneSimulatorErrorDomain Code 2”

Summary On iOS Safari (and WKWebView-based browsers), when a web page uses (or capture=user), the user can only ever hold one captured photo at a time. Each time the file picker is opened and the user takes a new photo using the camera, the newly captured image completely replaces the previously captured image in the input's files FileList. There is no way to accumulate multiple camera-captured photos across successive picker sessions. Steps to Reproduce Set up a web page with an element (with or without the capture attribute). Open the page in iOS Safari on an iPhone. Tap the file input — choose Take Photo from the action sheet. Capture a photo and tap Use Photo. Verify input.files.length === 1 (first photo is captured). Tap the same file input again — choose Take Photo again. Capture a second photo and tap Use Photo. Check input.files.length. Expected Result input.files.length should be 2 (or more), containing both the first and second captured photos. The browser should accumulate photos across

We’re unable to add external testing groups to our new builds for our app, Nox AI Wingman (https://apps.apple.com/in/app/nox-ai-wingman/id6753078092), because we keep facing a persistent, unexplained error. Some details: 3 calls + email updates with the team so far, we received no explanation other than directions to wait 48 hours and try again. We’re still unable to submit builds, with no word of any escalation or explanation for where the problem’s coming from. All agreements are signed, the build says “Ready to Submit”, all privacy related and other necessary fields have been filled out properly Browser Console shows the following error on submission: errors : [ { id : 112b2d19-6105-45c3-b941-3217d905fafc, status : 400, code : PARAMETER_ERROR.REQUIRED, title : A required parameter was not provided, detail : The parameter 'filter[build]' is required but was not provided, source : { parameter : filter[build] } } ] } Direct beta review submission gives us the following API error from apple: { code

Dear App Review Team, We would like to kindly follow up regarding our app submission, which has been in “Waiting for Review” status since Apr 10, 2026, with no progress update to date. We have also submitted 3 expedited review requests, plus 2 support requests email but unfortunately have not received any response yet. This prolonged delay is now significantly impacting our project timeline and scheduled deployment commitments. We understand review times can vary, but it has now been over a month without movement or communication. App ID: 6752937247

SharePlay Connectivity Issue: Asymmetric Connection Failures Between Vision Pro Generations Environment: Device 1: 2nd generation Vision Pro Device 2: 1st generation Vision Pro OS Version: visionOS 6 build 23O471 Custom App Version: Both devices running identical version Both devices fully updated to the same OS and app versions Issue Description: SharePlay connections exhibit asymmetric behavior based on invitation direction, despite successful FaceTime connectivity between devices: 2nd gen → 1st gen: SharePlay invitation fails consistently 1st gen → 2nd gen: SharePlay invitation succeeds consistently. FaceTime calls: Successful in both directions Impact: Users cannot reliably initiate SharePlay sessions from newer generation devices to older generation devices. The issue is isolated to SharePlay functionality, as standard FaceTime connectivity works bidirectionally and both devices run identical versions of the custom app.

I have two auto-renewable subscriptions (RedBird.Monthly and RedBird.yearly) that have been stuck in Waiting for Review status through 4 separate app version submissions and approvals. Each time I submit a new app version, the app itself gets approved and released, but the subscriptions remain in Waiting for Review and are never reviewed alongside it. I have: Added screenshots to both subscriptions under Review Information Filled in all required localization fields Submitted the app with a build attached each time Tried clicking Submit for Review on each subscription individually The subscriptions are part of a subscription group called RedBird Premium. The app is a Capacitor-based iOS app (com.redbird.wellness). Has anyone experienced this? Is there a specific step required to explicitly link subscriptions to an app version submission in the current App Store Connect UI? The In-App Purchases and Subscriptions section described in Apple's documentation does not appear on my version page. Any help app

Hello Apple Developer community, I am seeking help with a recurring App Store rejection under Guideline 2.1(a) - Performance - App Completeness. My app crashes on launch specifically on iOS 26.4.2 and I have confirmed this is a platform-level bug in React Native — not an issue with my application code. BACKGROUND My app is Highway Exit Food Finder — a navigation utility built with Expo SDK 55 / React Native 0.83. It has been in review for several weeks and has been rejected multiple times due to a crash on launch on iPad Air M3 and iPhone 17 Pro Max running iOS 26.4.2. THE CRASH Every crash log shows the same signature: Exception: EXC_CRASH (SIGABRT) Location: ObjCTurboModule::performVoidMethodInvocation Thread: com.meta.react.turbomodulemanager.queue The crash occurs during TurboModule initialization — BEFORE any JavaScript code runs. This means no application-level code change can fix it. CONFIRMED PLATFORM BUG This crash is documented in: github.com/facebook/react-native/issues/5

Hi, I have a SwiftUI work time screen with a rotating ring (60 tick marks, Canvas-based). While the app stays in foreground, rotation is fine. After the app is in background for a while and comes back to foreground, I consistently see one visual glitch: the ring makes one very short step in the opposite direction once then continues rotating clockwise normally So this is not a crash, only a visual reverse tick on resume. What I expect: no direction change after foreground resume continuous clockwise motion What I already tried: withAnimation(.linear(...).repeatForever(...)) + restart on scenePhase TimelineView (.animation and .periodic) with time-based angle angle with and without modulo wrapping wall-clock and monotonic time sources rotation via rotationEffect and also via Canvas geometry warmup delays after resume restoring original ring visuals (long/short tick marks) The effect is still reproducible. Question: What is the correct SwiftUI approach to implement a continuously rotating ring that stays direct

I did everything on 05-09-2026 and no update since then, account still pendant, no mail, no response for the 2 tickets I send, buet hey the charge was made! Document was uploaded, two tickets were opened, none has answer, I got charged for waiting, this is not good. I need answers for this!