I want to test running my iPhone app in the MacOs iPhone emulator. I installed the release version of my app from the store and it works 95%. So I'd like to test a new build , but I'm not sure how to install it.

Is this an uncaught C++ exception that could have originated from my code? or something else? (this report is from a tester) (also, why can't crash reporter tell you info about what exception wasn't caught?) (Per instructions here, to view the crash report, you'll need to rename the attached .txt to .ips to view the crash report) thanks! AudulusAU-2024-02-14-020421.txt

hi everyone. im new to xcode and wondering if anyone has any idea for what to do when your initial view controller keeps showing a black screen. ive done the following ensured Main storyboard file base name in info.pl is set to my storyboard. also under application scene manifest --> scene configurations --> application session role --> item 0 i have storyboard name as my storyboard and delegate class name as my SceneDelegate but I keep receiving this error 2024-02-13 22:42:47.452242-0500 PROJECT-NAME[11302:838011] [SceneConfiguration] Info.plist configuration "(no name)" for UIWindowSceneSessionRoleApplication contained UISceneDelegateClassName key, but could not load class with name "SceneDelegate". 2024-02-13 22:42:47.452641-0500 PROJECT-NAME[11302:838011] [SceneConfiguration] Info.plist configuration "(no name)" for UIWindowSceneSessionRoleApplication contained UISceneDelegateClassName key, but could not load class with name "SceneDelegate". 2024-02-13 22:42:47.456532-0500 PROJECT-NAME[11302:838011] [WindowScene] There is no scene delegate set. A scene delegate class must be specified to use a main storyboard file. the initial view controller box is checked for the correct controller (HomePageController) ive added print statements to my viewDidLoad() in my HomePageController (i guess one weird thing is that i cant set 'main interface' to my main storyboard in the deployment info section) im really not sure what else to do, and any help would be really appreciated. im a beginner so all of this is a bit difficult. this is my info.pl file: https://drive.google.com/file/d/1W-KOH3BjqgfJf10n9LM5bRTYHXQYM9ER/view?usp=sharing

Env: macOS 13.6.4, Xcode 15.2, MBP M1 Pro I am building/debugging a fairly simple C++ app which is meant to show some basic .dylib functionality. I received the Xcode project/source/libraries, which compile just fine, but when I attempt to run the "debug" version, it crashes before it gets to main(): Debug Navigator: Thread 1 Queue : com.apple.main-thread (serial) #0 0x0000000192544704 in __pthread_kill () #1 0x00000001049cab84 in pthread_kill () #2 0x0000000192489ae8 in abort () #3 0x00000002210fe948 in __report_load.cold.1 () #4 0x00000002210fe638 in __report_load () #5 0x00000001922401d8 in invocation function for block in dyld4::Loader::findAndRunAllInitializers(dyld4::RuntimeState&) const::$_0::operator()() const () #6 0x0000000192281e94 in invocation function for block in dyld3::MachOAnalyzer::forEachInitializer(Diagnostics&, dyld3::MachOAnalyzer::VMAddrConverter const&, void (unsigned int) block_pointer, void const*) const () #7 0x00000001922751a4 in invocation function for block in dyld3::MachOFile::forEachSection(void (dyld3::MachOFile::SectionInfo const&, bool, bool&) block_pointer) const () #8 0x00000001922202d8 in dyld3::MachOFile::forEachLoadCommand(Diagnostics&, void (load_command const*, bool&) block_pointer) const () #9 0x00000001922741cc in dyld3::MachOFile::forEachSection(void (dyld3::MachOFile::SectionInfo const&, bool, bool&) block_pointer) const () #10 0x0000000192281958 in dyld3::MachOAnalyzer::forEachInitializer(Diagnostics&, dyld3::MachOAnalyzer::VMAddrConverter const&, void (unsigned int) block_pointer, void const*) const () #11 0x000000019223c85c in dyld4::Loader::findAndRunAllInitializers(dyld4::RuntimeState&) const () #12 0x000000019223cc10 in dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&, dyld3::Array<dyld4::Loader const*>&) const () #13 0x000000019223cbec in dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&, dyld3::Array<dyld4::Loader const*>&) const () #14 0x000000019223cbec in dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&, dyld3::Array<dyld4::Loader const*>&) const () #15 0x0000000192240264 in dyld4::Loader::runInitializersBottomUpPlusUpwardLinks(dyld4::RuntimeState&) const::$_1::operator()() const () #16 0x000000019223cd90 in dyld4::Loader::runInitializersBottomUpPlusUpwardLinks(dyld4::RuntimeState&) const () #17 0x0000000192260984 in dyld4::APIs::runAllInitializersForMain() () #18 0x00000001922252d0 in dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) () #19 0x0000000192223e18 in start () Thread 2 Queue : com.apple.CoreAnalytics::Client XPC Send (serial) #0 0x0000000104bd50d4 in _dispatch_introspection_continuation_get_info () #1 0x0000000104bd667c in _dispatch_introspection_queue_item_dequeue_hook () #2 0x0000000104b9fbe0 in _dispatch_lane_serial_drain () #3 0x0000000104ba0d8c in _dispatch_lane_invoke () #4 0x0000000104bb0954 in _dispatch_workloop_worker_thread () #5 0x00000001049cbcc8 in _pthread_wqthread () And in the code window (Thread 1: signal SIGABRT at the line with the arrow): libsystem_kernel.dylib`: 0x1925446fc <+0>: mov x16, #0x148 0x192544700 <+4>: svc #0x80 -> 0x192544704 <+8>: b.lo 0x192544724 ; <+40> 0x192544708 <+12>: pacibsp 0x19254470c <+16>: stp x29, x30, [sp, #-0x10]! 0x192544710 <+20>: mov x29, sp 0x192544714 <+24>: bl 0x19253c8a8 ; cerror_nocancel 0x192544718 <+28>: mov sp, x29 0x19254471c <+32>: ldp x29, x30, [sp], #0x10 0x192544720 <+36>: retab 0x192544724 <+40>: ret I am not that familiar with Xcode debugging - where can I look to find why findAndRunAllInitializers() is failing?

I have the following problem: In the Moodle application there is a personalized screen to access some courses, for this a "mustache" file was added to the Moodle code with the following code: &lt;ion-list &gt; &lt;%#Cursos%&gt; &lt;%#.%&gt; &lt;ion-card style="height: 50%;"&gt; &lt;img alt="Silhouette of mountains" src="&lt;%wwwroot%&gt;/theme/almondb/pix/portada.jpg" /&gt; &lt;ion-card-header&gt; &lt;ion-card-title&gt;&lt;%fullname%&gt;&lt;/ion-card-title&gt; &lt;ion-card-subtitle&gt;&lt;%shortname%&gt;&lt;/ion-card-subtitle&gt; &lt;/ion-card-header&gt; &lt;ion-card-content&gt; &lt;ion-list&gt; &lt;a href="moodlemobile://&lt;%wwwroot%&gt;?redirect=/course/view.php?id=&lt;%id%&gt;" data-open-in="app" style="text-decoration: none;"&gt; &lt;ion-item lines="inset" detail="true"&gt; &lt;ion-label&gt; &lt;%fullname%&gt; &lt;/ion-label&gt; &lt;/ion-item&gt; &lt;/a&gt; &lt;/ion-list&gt; &lt;/ion-card-content&gt; &lt;/ion-card&gt; &lt;%/.%&gt; &lt;%/Cursos%&gt; &lt;/ion-list&gt; Custom URLs were used to achieve this. On Android the application works correctly, when you click it takes you to the course screen, however, on IOS it gives an error: "failed to load webpage with error unsupported url" I have tried the following solutions that I found in other forums &lt;meta http-equiv="Content-Security-Policy" content="default-src 'self' data: gap: *; script-src 'self' 'unsafe-inline' 'unsafe-eval' *; style-src 'self' 'unsafe-inline' 'unsafe-eval' *; media-src 'self' 'unsafe-inline' 'unsafe-eval' *; img-src 'self' 'unsafe-inline' 'unsafe-eval' * data:;"&gt; preference name="WKPort" value="8080" preference name="UseScheme" value="false" &lt;allow-navigation href="moodlemobile:*" /&gt; [Image Edited by Moderator to Remove Personal Information]

Hi all, I create apps for Apple and I've been encountering the issue that I cannot upload 4 or 5 apps in a day because they are rejected. It only allows me to upload one a day. Has anyone else encountered this issue/limit? Any advice or ways to resolve this issue? I have multiple apps to complete and upload but this issue has been delaying the process. Thanks in advance.

Hello there :) We have an iOS/iPadOS app that uses the ImageCaptureCore framework for PTP communication with cameras. In general, it is working just fine. But in "Xcode > Organizer > ’our app’ > Crashes" we get a good amount of different – yet similar – crashes in this framework. So we can just observe that a good amount of end-users get those crashes. But we are not able to reproduce them ourselves... I've checked the stack traces of the other threads but nothing suspicious got my attention. Any good idea of how to address these crashes shown below? Happens on iOS 15–17. Thanks!

Xcode Version 15.2 (15C500b) After upgrading Xcode from 14 to 15.2 I am not able to attach system extension (packettunnel) process to Instruments tools for memory debugging. Same is working fine with Xcode 14. Error displayed: "Process No Longer Exists". But the service is running and is listed in process list. % ps -ax | grep -i pkttunnel | grep -v grep 61910 ?? 0:01.04 /Library/SystemExtensions/5F4AF6EF-****-****-****-F11****9CE78/com.******.client.*****-Client.***ui.***pkttunnel.systemextension/Contents/MacOS/com.******.client.*****-Client.***ui.***pkttunnel.systemextension Note: I am able to attach a normal program to Instruments tool for memory debugging, I have noticed this issue with system extension processes only.

When click on run in xcode, i can see the trust popup on the device screen. but for turst that one i am going inside Settings&gt;General&gt;Device Management - i can see my developer account notification but when i click on that unable to trust that device, and i had restart my device and tried again but same issue. can any one please help me on this. Thanks!

Xcode Version 15.2 in general is very, very slow when debugging. If I get to that, often, xcode just shows a message "Preparing iPhone 15 Pro Joride. Xcode will continue when the operation completes" This box will stay there for at least 3 min. Then it is follow by a message about a developer image not being able to get mounted: "Previous preparation error: The developer disk image could not be mounted on this device.. Error mounting image: 0xe8000115 (kAMDMobileImageMounterDevicePropertyQueryFailure: Failed to query device property.)" If I eventually do manage to debug my app, it is soooooo slow. The launchscreen is there for easily 20 seconds (I'm guessing debugger is trying to attach during this time). When there are breakpoints present at all, things just occur very very slowly, expecially when trying to PO variables. The app itself runs fine though. I've noticed there is a checkbox for this device that says 'Connect via network'. This clearly seems to be broken for my combination of factors, so I wanted to uncheck it. Not possible! For those of use with a similar experience, any suggestions? (I did try to power cycle both computer and iPhone, but that did not change much. Both devices are connected to the same home wifi which has no special setup or restrictions)

I'm trying to use Xcode debugging without an internet connection but on the iOS device I get the error that it is impossible to verify the app without the connection. Is there a way to avoid this problem? Are there any solutions? Thanks

I am getting below crash in reactive swift library. Will really appreciate any help in resolving it. Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_PROTECTION_FAILURE at 0x000000016b33bfe0 Exception Codes: 0x0000000000000002, 0x000000016b33bfe0 VM Region Info: 0x16b33bfe0 is in 0x16b338000-0x16b33c000; bytes after start: 16352 bytes before end: 31 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL MALLOC_SMALL 15b800000-15c000000 [ 8192K] rw-/rwx SM=PRV GAP OF 0xf338000 BYTES ---&gt; STACK GUARD 16b338000-16b33c000 [ 16K] ---/rwx SM=NUL ... for thread 0 Stack 16b33c000-16b438000 [ 1008K] rw-/rwx SM=SHM thread 0 Termination Reason: SIGNAL 11 Segmentation fault: 11 Terminating Process: exc handler [1677] Triggered by Thread: 0 Thread 0 name: Thread 0 Crashed: 0 libswiftCore.dylib 0x000000019371c5a8 getCache(swift::TargetTypeContextDescriptorswift::InProcess const&amp;) + 8 (Metadata.cpp:479) 1 libswiftCore.dylib 0x000000019371d108 swift_getGenericMetadata(swift::MetadataRequest, void const* const*, swift::TargetTypeContextDescriptorswift::InProcess const*) + 56 (Metadata.cpp:937) 2 ReactiveSwift 0x0000000107cdef74 __swift_instantiateGenericMetadata + 28 (:0) 3 ReactiveSwift 0x0000000107cfe3b8 specialized Signal.Core.send(:) + 540 (Signal.swift:115) 4 ReactiveSwift 0x0000000107d2b408 Signal.Observer.send(:) + 20 (Signal.Observer.swift:111) 5 ReactiveSwift 0x0000000107cf7390 closure #3 in closure #1 in closure #1 in Signal&lt;&gt;.observeSwitchToLatest(::) + 188 (Flatten.swift:677) 6 ReactiveSwift 0x0000000107d2b408 Signal.Observer.send(:) + 20 (Signal.Observer.swift:111) 7 ReactiveSwift 0x0000000107d195f8 Signal.Core.tryToCommitTermination() + 604 (Signal.swift:231) 8 ReactiveSwift 0x0000000107cfe3b8 specialized Signal.Core.send(:) + 540 (Signal.swift:115) 9 ReactiveSwift 0x0000000107d2b408 Signal.Observer.send(:) + 20 (Signal.Observer.swift:111) 10 ReactiveSwift 0x0000000107cf7390 closure #3 in closure #1 in closure #1 in Signal&lt;&gt;.observeSwitchToLatest(::) + 188 (Flatten.swift:677) 11 ReactiveSwift 0x0000000107d2b408 Signal.Observer.send(:) + 20 (Signal.Observer.swift:111) 12 ReactiveSwift 0x0000000107d195f8 Signal.Core.tryToCommitTermination() + 604 (Signal.swift:231) 13 ReactiveSwift 0x0000000107cfe3b8 specialized Signal.Core.send(:) + 540 (Signal.swift:115) 14 ReactiveSwift 0x0000000107d2b408 Signal.Observer.send(:) + 20 (Signal.Observer.swift:111) 15 ReactiveSwift 0x0000000107cf7390 closure #3 in closure #1 in closure #1 in Signal&lt;&gt;.observeSwitchToLatest(:_:) + 188 (Flatten.swift:677) Here is Stack trace for the crash. crashlog.txt

We have tested this at our end on the latest mac version 'Sonoma 14.3 version' and application is launching successfully. But when i submit the app on App Store it will reject by given this reason(We were unable to review your app as it crashed on launch on Mac running macOS 14.3.) Thanks !!.

I'm experiencing a strange app crash that I'm having a tough time debugging. It seems to happen when calling PKPassLibrary.passes(of:), but I'm unable to reproduce it. We're using a third party crash reporter, which I know can corrupt crash reports - does that seem to be the case here? The whole report is available here: https://gist.github.com/kylebshr/3ed29dd47ee05f2a5e47993bf986b8f4 0 libsystem_kernel.dylib +0x1174 _mach_msg2_trap 1 libsystem_kernel.dylib +0xf0c _mach_msg2_internal 2 libsystem_kernel.dylib +0xe24 _mach_msg_overwrite 3 libsystem_kernel.dylib +0xc64 _mach_msg 4 libdispatch.dylib +0x1eefc __dispatch_mach_send_and_wait_for_reply 5 libdispatch.dylib +0x1f29c _dispatch_mach_send_with_result_and_wait_for_reply 6 libxpc.dylib +0x106d0 _xpc_connection_send_message_with_reply_sync 7 Foundation +0x37bcc ___NSXPCCONNECTION_IS_WAITING_FOR_A_SYNCHRONOUS_REPLY__ 8 Foundation +0x202e4 -[NSXPCConnection _sendInvocation:orArguments:count:methodSignature:selector:withProxy:] 9 CoreFoundation +0x31b58 ____forwarding___ 10 CoreFoundation +0x17294c ___forwarding_prep_0___ 11 PassKitCore +0x1c5e94 -[PKPassLibrary _copyPassesOfType:withRetries:] 12 PassKitCore +0x1b0650 -[PKPassLibrary passesOfType:] 13 Mercury +0x3758c _mh_execute_header 14 Mercury +0x604bcc main 15 Mercury +0x9e0d34 main 16 Mercury +0x9e0f88 main 17 Mercury +0xa320ec main 18 Mercury +0x9ea514 main 19 Mercury +0x9eaa58 main 20 Mercury +0x9eaa08 main 21 Mercury +0x9f1650 main 22 Mercury +0x9f16f0 main 23 libdispatch.dylib +0x42fc __dispatch_client_callout 24 libdispatch.dylib +0x77b4 __dispatch_continuation_pop 25 libdispatch.dylib +0x1b5bc __dispatch_source_latch_and_call 26 libdispatch.dylib +0x1a18c __dispatch_source_invoke 27 libdispatch.dylib +0x128a4 __dispatch_main_queue_drain 28 libdispatch.dylib +0x125ac __dispatch_main_queue_callback_4CF 29 CoreFoundation +0x36f98 ___CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ 30 CoreFoundation +0x33ca4 ___CFRunLoopRun 31 CoreFoundation +0x333f4 _CFRunLoopRunSpecific 32 GraphicsServices +0x34f4 _GSEventRunModal 33 UIKitCore +0x22c89c -[UIApplication _run] 34 UIKitCore +0x22bed8 _UIApplicationMain 35 UIKitCore +0x456594 0x18a42d594 (0x18a42d530 + 100) 36 Mercury +0x1bdff4 main 37 dyld +0x5dc8 start

Is it even possible or part of VisionOS? Thanks, Colin

Recently I updated to Xcode 14.0. I am building an iOS app to convert recorded audio into text. I got an exception while testing the application from the simulator(iOS 16.0). [SpeechFramework] -[SFSpeechRecognitionTask handleSpeechRecognitionDidFailWithError:]_block_invoke Ignoring subsequent recongition error: Error Domain=kAFAssistantErrorDomain Code=1101 "(null)" Error Domain=kAFAssistantErrorDomain Code=1107 "(null)" I have to know what does the error code means and why this error occurred.

Hello. I have two crash reports that are likely related, with the following kernel triage: crash report 1: VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter crash report 2: VM - Compressor failed a blocking pager_get Both reports seem to indicate that the crash may be happening during (and perhaps caused by) the call to RubyLocalDB.saveStoreMetadata. I have attached the reports below. I would really appreciate any insight into what the kernel triages indicate based on the stack traces. Thank you. crash_report_1.crash crash_report_2.crash

The examination is being rejected due to a conflict issue in the webview. It's a log file, what's the reason? When tested with the device, it works fine.

We are getting many crash reports from users that just updated to Sonoma 14.3 on arm64 macs. We can reproduce these types of crashes on arm64 14.3 machines only (not Intel 14.3, other versions of macOS, etc). A typical crash report: Code Type: arm64 Parent Process: launchd [1] Date/Time: 2024-01-27T15:51:54.999Z Launch Time: 2024-01-27T15:51:43Z OS Version: Mac OS X 14.3.0 (23D56) Report Version: 104 Exception Type: SIGILL Exception Codes: ILL_NOOP at 0x2e23fc03 Crashed Thread: 9 Thread 9 Crashed: 0 QuartzCore 0x0000000188923428 CA::OGL::PathRenderer::PathRenderer(CA::OGL::Context&, CA::Mat2 const&, CA::Bounds const&, bool, bool, bool) + 268 1 QuartzCore 0x0000000188922d90 CA::OGL::PathFiller::PathFiller(CA::OGL::Context&, CA::Mat2 const&, CA::Bounds const&, CA::OGL::PathCubic*, int, CA::OGL::PathRect*, int, CA::OGL::PathFiller::ScanlinePoint*, int, bool, bool) + 48 2 QuartzCore 0x000000018885db28 CA::CG::fill_path(CA::CG::Renderer&, CGPath const*, CA::CG::StrokeParameters const*, CA::Rect const*, CA::ScanConverter::FillRule, CA::Mat2 const&, bool) + 2724 3 QuartzCore 0x00000001887ffe7c CA::CG::DrawOp::render(CA::CG::Renderer&) const + 1520 4 QuartzCore 0x00000001887fce5c CA::CG::Queue::render_callback(void*) + 1472 5 libdispatch.dylib 0x0000000180448910 _dispatch_client_callout + 16 6 libdispatch.dylib 0x000000018044ff74 _dispatch_lane_serial_drain + 952 7 libdispatch.dylib 0x00000001804509d4 _dispatch_lane_invoke + 376 8 libdispatch.dylib 0x000000018045b61c _dispatch_root_queue_drain_deferred_wlh + 284 9 libdispatch.dylib 0x000000018045ae90 _dispatch_workloop_worker_thread + 400 10 libsystem_pthread.dylib 0x00000001805f6114 _pthread_wqthread + 284 11 libsystem_pthread.dylib 0x00000001805f4e30 start_wqthread + 4 Thread 0: 0 libsystem_kernel.dylib 0x00000001805bb5a8 kevent_id + 8 1 libdispatch.dylib 0x000000018046bff4 _dispatch_event_loop_wait_for_ownership + 432 2 libdispatch.dylib 0x0000000180457f94 DISPATCH_WAIT_FOR_QUEUE + 336 3 libdispatch.dylib 0x0000000180457b5c _dispatch_sync_f_slow + 144 4 QuartzCore 0x00000001887e36a0 CABackingStoreGetFrontTexture(CABackingStore*, CGColorSpace*) + 184 5 QuartzCore 0x00000001887d374c -[NSObject(CARenderValue) CA_prepareRenderValue] + 228 6 QuartzCore 0x0000000188a2545c CA::Layer::prepare_contents(CALayer*, CA::Transaction*) + 188 7 QuartzCore 0x00000001887d0798 CA::Layer::prepare_commit(CA::Transaction*) + 276 8 QuartzCore 0x0000000188950e4c CA::Context::commit_transaction(CA::Transaction*, double, double*) + 676 9 QuartzCore 0x00000001887ae8f0 CA::Transaction::commit() + 644 10 AppKit 0x0000000183fdcb18 __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 268 11 AppKit 0x0000000184992f04 ___NSRunLoopObserverCreateWithHandler_block_invoke + 60 12 CoreFoundation 0x00000001806d6d80 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 32 13 CoreFoundation 0x00000001806d6c6c __CFRunLoopDoObservers + 528 14 CoreFoundation 0x00000001806d629c CFRunLoopRun + 772 15 CoreFoundation 0x00000001806d593c CFRunLoopRunSpecific + 604 16 HIToolbox 0x000000018ac9e448 RunCurrentEventLoopInMode + 288 17 HIToolbox 0x000000018ac9e0d8 ReceiveNextEventCommon + 216 18 HIToolbox 0x000000018ac9dfdc _BlockUntilNextEventMatchingListInModeWithFilter + 72 19 AppKit 0x0000000183eb4ed0 DPSNextEvent + 656 20 AppKit 0x000000018469feec -[NSApplication(NSEventRouting) nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 712 21 AppKit 0x0000000183ea837c -[NSApplication run] + 472 22 acord 0x0000000100c45290 P110TARGETAPP$$TTARGETAPPLICATION$$$_EVENTLOOP (p110TargetApp.pas:5781) 23 acord 0x0000000100bc82e8 PASCALMAIN (Accord.pas:154) 24 acord 0x000000010159ab40 FPC_SysEntry + 28 25 acord 0x000000010156f770 FPC_SYSTEMMAIN + 76 26 acord 0x0000000100bc814c main + 8 27 ??? 0x00000001802790e0 0x0 + 0 {....} Thread 14: 0 ??? 0x0000000000000000 0x0 + 0 Thread 9 crashed with arm64 Thread State: x21: 0x000000016f7bb270 x2: 0x0000000169a00658 x16: 0x00000001887fef60 x3: 0x000000016f7b6a20 x22: 0x000000016f7b6a20 x4: 0x0000000000000000 x17: 0x00000001887feeb0 cpsr: 0x0000000060001000 x5: 0x0000000000000000 x23: 0x0000000000000000 x6: 0x0000000000000001 x18: 0x0000000000000000 x10: 0x0000000188af7000 lr: 0x0000000188922d90 x7: 0x0000000000000000 x24: 0x0000000169a00658 x11: 0x0000000000000000 x8: 0x0000000000000007 x19: 0x000000016f7b6a70 x25: 0x0000000188b0d968 x9: 0x0000000000000001 x12: 0x0000000000000008 fp: 0x000000016f7b6960 x26: 0x000000016f7ca270 x13: 0x0000000000000009 pc: 0x0000000188923428 x27: 0x0000000000000001 x14: 0x0000000000000001 x20: 0x000000016f7b8a70 x0: 0x000000016f7ca270 sp: 0x000000016f7b6940 x28: 0x0000000000000000 x15: 0x0000000000000012 x1: 0x0000000144808e00 In Xcode we might see a divide by zero like: 0x189247428 <+268>: fdiv EXC_BAD_INSTRUCTION (code=1, subcode=0x2e23fc03) Any help with interpreting/debugging this type of crash would be appreciated.

Hello! Could please someone help me with such question: in Xcode I could see that there are two possible destinations for Apple Vision - Apple vision vs Apple vision (Designed for iPad). So while I tried to test my app, I noticed that it is possible that my app crashes on Apple Vision for visionOs sdk, but runs on the designed for iPad version and when launched they looks differently. Does it mean that if I want to make sure that my app works correctly for real device, then I should test it on the Apple Vision for visionOs sdk?