“DTiPhoneSimulatorErrorDomain Code 2”

This is unrelated to WKWebView and to the JavaScript-injection issue we were discussing. The app isn't reaching any code that uses WKWebView. yes i know but when its occured wanted to share with you For a launch crash like this, the fastest progress is usually a report to the .NET MAUI / Xamarin issue tracker, what is your suggestion? should i I clean install Rider macOS 26.1.2 (latest and simulator problem solved version) and Xcode & emulators? Run your Xcode 26 / iOS 26 SDK build on the iPhone 13 connected via USB. In Safari on the Mac, choose Develop → [Your iPhone] → [the entry for the WKWebView inside your app]. The entry will be labeled with your app's name or with the URL the WKWebView is currently showing — not Safari, which is a separate process. With the JavaScript console open, trigger the operation in your app that's failing. The errors (or silence) on the console will tell us which of the four scenarios from my previous message you're in. The test you described in NOTE-1 was the page

Thanks for sending the three samples and the code snippet. They confirm the symptom (NSInvalidArgumentException: object cannot be nil from [__NSArrayM insertObject:atIndex:]) but don't yet narrow the source. I traced the symbol from your stack into the ShareSheet binary. The crash lands inside the block that processes activity items in loadItemProvidersForRequest:activity:completion:, in the branch that handles NSURL items. That branch resolves metadata for the file URL via LaunchServices and FileProvider, builds a security context, and constructs an NSArray from the result. The NSArray construction has no nil guard, so any nil reaching it throws the exception you see. On an iPhone 16 running iOS 26.4, I built a small reproducer that presents a downloaded PDF four ways: UIDocumentInteractionController.presentPreview, QLPreviewController, UIActivityViewController with the file URL, and UIActivityViewController with an NSItemProvider built from the PDF's bytes. None crashed. The three file-URL paths pr

Hi Suyog, I went through the exact same issue with AddFive, a fitness app using AVSpeechSynthesizer for voice coaching over AVAudioSession (.playback). Two 2.5.4 rejections with the same boilerplate before it went through. What I believe made the difference: a screen recording attached to the Resolution Center reply showing audio actively playing during a workout session, so the reviewer could see and hear the feature in context without having to find it themselves. Good luck, you're clearly doing everything right.

Intermittent bugs are still worth filing — a Feedback Report doesn't need to reliably reproduce. It needs to give engineering enough information to identify the failure when it happens and to correlate against the server-side logs. A few things that make this kind of report useful: A sample project that uses the same receivedTurnEventForMatch → loadMatch(withID:) path. If you can extract that flow out of your game into a small standalone app that two test accounts can play against each other, that's ideal. If extracting is impractical, your actual app build can work too — engineering may follow up with what would help most. Logging that captures, for each receivedTurnEventForMatch: the timestamp, the match ID, the local player ID, the reported current participant, and the matchData state at that moment. Then for each retry: the timestamp, what was returned, and whether it matched the previous state. The match IDs and approximate timestamps from past occurrences you've observed. Engineering can cross-

Thanks for sending the crash report. The simulator launch crash is a different issue from the JavaScript-injection problem we were tracking, and the good news is it doesn't have to block the JS debugging — more on that at the end. The simulator crash is a code-signing failure at dynamic load The most informative parts of the crash report: Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page Crashing thread: dyld_sim, in mach_o::UnsafeHeader::forEachLoadCommand / forEachSegment The crash happens about 3 ms after launch — the dynamic linker is still loading binaries from the .app bundle and your code never runs. What this means: as dyld maps pages of a binary into memory, the kernel verifies each page against the binary's code signature. One page doesn't match, the kernel terminates the process, and the crash report points at the mapped-file region that failed. The address (0x1014c4000) with Invalid Page wording typically indicates a page-hash mismatch — e

I am getting that error as well with one app that I am developing, while another app that I made works fine with, as far as I know, the same settings etc., and very similar code.

Thanks for the question. A few clarifications first: The naming convention you're describing (IMG_XXXX, files in a DCIM folder) comes from the DCF specification — Design rule for Camera File system, established by JEITA. Most digital cameras, including iOS devices, follow it for interoperability with computers and other devices. The system Camera app uses DCF naming, and that behavior isn't user-configurable. You can't change how the built-in Camera app names the files it creates. However, you can build your own camera app that uses any naming convention you like — including IMG_YYYYMMDD_HHMMSS for photos and VID_YYYYMMDD_HHMMSS for videos. The same public frameworks the Camera app uses are available to every developer. One thing to keep in mind: even after you give a captured file a custom filename, the Photos app displays photos by date in its main UI rather than by filename. Filenames are visible in the asset's info panel, not the main grid view. So a custom filename helps when you export or share files, o

Hi jono_id4me, sorry for the slow reply. Still nothing on my side. Request 2C4HJDWYJ6 has now been under review for 85 days from the Feb 23 submission. Apple Developer Support confirmed on May 8 that it's in the pipeline to be onboarded but no concrete date. How about you? Any movement on your side since February? And did Apple ever validate your relay/PIR setup, or is it just sitting in the queue too? If you're up for it, would be useful to compare notes — bundle IDs, dates, what your support advisor has said. Two data points are better than one when neither of us can get a timeline. Thanks, Levan

Hey @anmac1789, It sounds like you'd like to make a camera app, so I recommend that you start with AVCam: Building a camera app. The underlying code for the system's Camera app is not available, and we can't provide details about it, but the sample code project I linked to above can hopefully help you with your camera app development! -- Greg

Thanks for the post, what about to retrieve the friendly model name from the command line, I normally use system_profiler. system_profiler SPHardwareDataType | grep Model Name Or we can just remove the label with: system_profiler SPHardwareDataType | awk -F': ' '/Model Name/ {print $2}' Hope this helps. Resources: https://discussions.apple.com/thread/5988473 https://discussions.apple.com/docs/DOC-250009356 Albert
  Worldwide Developer Relations.

Thanks for the reply but when deploy to the simulator its crashing so that i can't test anything ( my setup is macOS 26, xCode 26.4.1, 26.5 simulators, macOS Rider 26.1.2 ) here ise crash report Translated Report (Full Report Below) Process: XsentiusMaui [37730] Path: /Users/USER/Library/Developer/CoreSimulator/Devices/F24D336A-217A-4B3C-9D86-B11FF5A3C57C/data/Containers/Bundle/Application/054985D3-AA75-4CCE-A103-35EC0BE523B0/XsentiusMaui.app/XsentiusMaui Identifier: com.cozbim.xsentiusmobile Version: 1.0.1 (101) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd_sim [37350] Coalition: com.apple.CoreSimulator.SimDevice.F24D336A-217A-4B3C-9D86-B11FF5A3C57C [7708] Responsible Process: SimulatorTrampoline [1010] User ID: 501 Date/Time: 2026-05-19 20:09:33.7484 +0300 Launch Time: 2026-05-19 20:09:33.6347 +0300 Hardware Model: Mac16,1 OS Version: macOS 26.5 (25F71) Release Type: User Crash Reporter Key: 307E060A-0B57-9A0D-D769-4CCF07BED703 Incident Identifier: DDDD5089-C8EA-4AD0-BD3B-5398