Yet another issue with debugging on iOS (real device)


I’m having troubles with trying to debug an iOS app to my iPad. It’s the first time I’m trying iOS debugging since I moved to Mac OS 13, so I already faced some issues. Now, I’m puzzled.
Xojo goes through the build process and, near the end, the process ios-deploy crashes:

Process: ios-deploy [1529]
Path: /Volumes/VOLUME/*/
Identifier: ios-deploy
Version: ???
Code Type: ARM-64 (Native)
Parent Process: Xojo [1309]
Responsible: Xojo [1309]
User ID: 501

Date/Time: 2023-03-10 19:39:44.9833 +0100
OS Version: macOS 13.2.1 (22D68)
Report Version: 12
Anonymous UUID: E9223FE8-AFD9-1127-2C5E-B25AFC7CAB54

Time Awake Since Boot: 520 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000068
Exception Codes: 0x0000000000000001, 0x0000000000000068

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1529]

VM Region Info: 0x68 is not in any region. Bytes before following region: 105553518919576
MALLOC_NANO (reserved) 600018000000-600020000000 [128.0M] rw-/rwx SM=NUL …(unallocated)

Thread 0 Crashed:: Dispatch queue:
0 libsystem_c.dylib 0x1a0ce9a10 flockfile + 28
1 libsystem_c.dylib 0x1a0ce9a0c flockfile + 24
2 libsystem_c.dylib 0x1a0cf0148 fread + 44
3 ios-deploy 0x1040c80c4 mount_developer_image + 160
4 ios-deploy 0x1040ca238 setup_lldb + 92
5 ios-deploy 0x1040ca470 launch_debugger_and_exit + 20
6 ios-deploy 0x1040ce9ac handle_device + 1608
7 MobileDevice 0x104aa5bb0 _AMDDeviceAttachedCallbackv3 + 448
8 MobileDevice 0x1049f9a84 _USBMuxCustomRunLoopSourcePerformCallback + 1196
10 CoreFoundation 0x1a0ef999c __CFRunLoopDoSource0 + 176
11 CoreFoundation 0x1a0ef970c __CFRunLoopDoSources0 + 244
12 CoreFoundation 0x1a0ef8310 __CFRunLoopRun + 836
13 CoreFoundation 0x1a0ef7878 CFRunLoopRunSpecific + 612
14 CoreFoundation 0x1a0f7e7e8 CFRunLoopRun + 64
15 ios-deploy 0x1040cf9e8 main + 1652
16 dyld 0x1a0aefe50 start + 2544

And, of course, Xojo reports it couldn’t launch the app for debugging.
ios-deploy is part of Xojo.
Has anyone seen similar behaviors recently?
How may I debug this? Console doesn’t seem to show relevant logs and I can’t manually start ios-deploy from a terminal window (to show all the logging strings).

That crash log seems to indicate that it’s crashing while trying to get a file lock on the developer image. That path that’s in the crash log, is that accurate or is that something you anonymized?

Path: /Volumes/VOLUME/*/

If that’s correct, are you running Xojo from a DMG or other write protected drive?

My internal hard disk has a partition where I install the applications I use. Xojo is on this partition, thus the path. It’s neither protected nor a DMG, just another partition in the same APFS container.

Just for the sake of checking, I copied Xojo temporarily to the /Applications folder and the result is the same.

Thanks for your answer.

Ok, I found the problem. XCode was installed on an external (USB) disk, because 22 GB is too much for my small internal hard disk of 256 GB. Until now, this was not a problem; XCode and Xojo happily ran with that setup.

I tried putting XCode back to the internal /Applications folder and… it works. But now my disk is smaller than ever.

Looks like Mac OS 13 broke something more. No ideal solution :man_shrugging: