Note:
That issue seems to occur only when you return the custom interface ViewController for TVInterfaceCreating protocol.
laesde
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
We're facing quite similar issue.
Short brief of our situations:
we pushed app to appstore connect at 08.11.2022
app was built using Xcode 13.4.1 (Build version 13F100)
bitcode enabled
Based on latest feedback I understand that apps that are built using the XCode 13.x but published after the XCode 14.1 release should work fine. Anyway we're facing the crashes that occur on devices with iOS 11.x (11.1, 11.2.5)
Crashlog:
Incident Identifier: A0A546D9-A226-40FA-A274-D3F233CEDE5F
Hardware Model: iPhone7,1
Process: myapp [1156]
Path: /private/var/containers/Bundle/Application/90DA7BAA-579C-471B-B0FF-39336888B2A8/myapp.app/myapp
Identifier: com.myapp.app
Version: 1667918418 (9.6.1)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: com.myapp.app [480]
Date/Time: 2022-11-13 12:43:12.9491 +0700
Launch Time: 2022-11-13 12:43:12.4916 +0700
OS Version: iPhone OS 11.2.5 (15D60)
Baseband Version: 6.30.04
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Description: DYLD, Library not loaded: /usr/lib/swift/libswiftCoreData.dylib | Referenced from: /var/containers/Bundle/Application/90DA7BAA-579C-471B-B0FF-39336888B2A8/myapp.app/myapp | Reason: image not found
Triggered by Thread: 0
Thread 0 Crashed:
0 dyld 0x00000001014d2f48 __abort_with_payload + 8
1 dyld 0x00000001014d271c abort_with_payload_wrapper_internal + 100 (terminate_with_reason.c:71)
2 dyld 0x00000001014d2748 abort_with_payload + 12 (terminate_with_reason.c:93)
3 dyld 0x00000001014a8498 dyld::halt(char const*) + 312 (dyld.cpp:3824)
4 dyld 0x00000001014ab714 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, un... + 7376 (dyld.cpp:6202)
5 dyld 0x00000001014a521c _dyld_start + 68
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000006 x1: 0x0000000000000001 x2: 0x000000016f79a520 x3: 0x0000000000000092
x4: 0x000000016f79a120 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000a60
x8: 0x0000000000000020 x9: 0x0000000000000009 x10: 0x6c504b2f38413242 x11: 0x4b2f7070612e7375
x12: 0x20200a73756c504b x13: 0x203a6e6f73616552 x14: 0x6f6e206567616d69 x15: 0x00646e756f662074
x16: 0x0000000000000209 x17: 0x000000008000001f x18: 0xfffffff00f49925c x19: 0x0000000000000000
x20: 0x000000016f79a120 x21: 0x0000000000000092 x22: 0x000000016f79a520 x23: 0x0000000000000001
x24: 0x0000000000000006 x25: 0x0000000100664000 x26: 0x00000001014e6000 x27: 0x00000001014e5f88
x28: 0x000000016f79bb20 fp: 0x000000016f79a0f0 lr: 0x00000001014d271c
sp: 0x000000016f79a0b0 pc: 0x00000001014d2f48 cpsr: 0x00000000
Binary Images:
0x100664000 - 0x100f1bfff myapp arm64 <570e.......
@edford Do you know maybe what's the status of the potential fix for the mentioned issue?