My app's top crash is a mysterious one and I can't seem to figure it out. It always crashes on
_objc_fatalv(unsigned long long, unsigned long long, char const*, char*)
But the stack traces include a few different possible culprits like
NavigationBridge_PhoneTV.pushTarget(isDetail:)
UIKitNavigationBridge.update(environment:)
ViewRendererHost.updateGraph()
UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled
Crash reports here:
2024-12-02_21-37-21.7864_-0600-1e78918e5586309b96a1c2986ff722778dec8a77.crash
2024-12-02_19-18-29.1251_-0500-a2fc5513683cd647b4adbbe03cc59e4a09237b5f.crash
2024-12-01_11-59-09.8888_-0500-9eb224ab3d37e76d0b966ea83473f584ac3bbe18.crash
2024-11-28_17-17-38.4808_+0100-46208989f016fbefd16c30873a88c2ef61dd91a1.crash
Hopefully someone here can shed some light. For context we use a lot of UIHostingController's to bridge our SwiftUI views.
Post
Replies
Boosts
Views
Activity
Hey there! My app's top crash is a mysterious one and I can't seem to figure it out. Hopefully someone here can shed some light. For context we use a lot of UIHostingController's to bridge our SwiftUI views.
Crashed: com.apple.main-thread
0 libsystem_kernel.dylib 0x13ec4 __abort_with_payload + 8
1 libsystem_kernel.dylib 0x33bec abort_with_payload_wrapper_internal + 104
2 libsystem_kernel.dylib 0x33b84 abort_with_payload_wrapper_internal + 30
3 libobjc.A.dylib 0xbea0 _objc_fatalv(unsigned long long, unsigned long long, char const*, char*) + 116
4 libobjc.A.dylib 0xbe2c _objc_fatalv(unsigned long long, unsigned long long, char const*, char*) + 30
5 libobjc.A.dylib 0xb040 weak_register_no_lock + 396
6 libobjc.A.dylib 0xa9bc objc_initWeak + 440
7 libswiftCore.dylib 0x43abe8 swift_unknownObjectWeakInit + 92
8 SwiftUI 0xf40cc NavigationBridge_PhoneTV.pushTarget(isDetail:) + 376
9 SwiftUI 0xf9490 UIKitNavigationBridge.update(environment:) + 1060
10 SwiftUI 0x5b51c UIHostingController._update(environment:) + 156
11 SwiftUI 0x96a30 _UIHostingView.updateEnvironment() + 3484
12 SwiftUICore 0xa0d0a0 closure #1 in ViewRendererHost.updateGraph() + 364
13 SwiftUICore 0xa0ca08 ViewRendererHost.updateGraph() + 180
14 SwiftUICore 0xa0d7d4 closure #1 in ViewRendererHost.render(interval:updateDisplayList:targetTimestamp:) + 368
15 SwiftUICore 0xa0b0d4 ViewRendererHost.render(interval:updateDisplayList:targetTimestamp:) + 556
16 SwiftUI 0x8f1634 UIHostingViewBase.renderForPreferences(updateDisplayList:) + 168
17 SwiftUI 0x8f495c closure #1 in UIHostingViewBase.requestImmediateUpdate() + 72
18 SwiftUI 0xcc700 thunk for @escaping @callee_guaranteed () -> () + 36
19 libdispatch.dylib 0x2370 _dispatch_call_block_and_release + 32
20 libdispatch.dylib 0x40d0 _dispatch_client_callout + 20
21 libdispatch.dylib 0x129e0 _dispatch_main_queue_drain + 980
22 libdispatch.dylib 0x125fc _dispatch_main_queue_callback_4CF + 44
23 CoreFoundation 0x56204 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16
24 CoreFoundation 0x53440 __CFRunLoopRun + 1996
25 CoreFoundation 0x52830 CFRunLoopRunSpecific + 588
26 GraphicsServices 0x11c4 GSEventRunModal + 164
27 UIKitCore 0x3d2eb0 -[UIApplication _run] + 816
28 UIKitCore 0x4815b4 UIApplicationMain + 340
29 (MyApp) 0x1a7e0 main + 8 (main.swift:8)
30 ??? 0x1bf97eec8 (Missing)
I'm dealing with a problem uploading our release binaries that is completely perplexing. If I use the ITMS Transporter desktop app to upload my IPA, everything works fine. If I use the ITMS Transporter command line interface (which i'm calling from inside the desktop app's directory /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter -m upload...) to upload my IPA, I get the following error
ERROR ITMS-90529: Invalid package. Applications built with sdk 9.0 or later must be packaged as proper IPA files.
No idea why this error is coming up. I can also use altool to upload my binaries successfully. The issue is altool is being deprecated and I need to be able to use the ITMS command line interface as part of some deployment scripts we have.
Please help!