How We Fixed the Dreaded 0xdead10cc Crash
https://inessential.com/2020/02/13/how_we_fixed_the_dreaded_0xdead10cc_cras
Post
Replies
Boosts
Views
Activity
Thanks for the information! I suppose Apple thinks it's an irrelevance. Or maybe they think it's a shame.
Thank you! Look forward to a reply.
Yes, the error is indeed related to libswift_Concurrency.dylib in latest SDK. But my app and dependencies use async/await and require back deploy, so there is no way to exclude libswift_Concurrency.dylib. 😢
Have you tried disabling bitcode? I tested it with a temporary project, and after completely disabling bitcode, there was no problem. But my app contains the apple watch app, which is unable to disable bitcode.
Thanks for the info. It looks like our friends at Apple have updated the Release Notes 😂. But the workaround is not working because once an app contains Apple Watch target, there is no way to turn off bitcode. Still stuck.
⬆️ I believe the guy upstairs :) I will try it later.
DTS ticket burned. 😂
Thanks for the info! I'm glad the issue was fixed, even though it took a few months. 😂 I'm deciding whether to upgrade to Xcode 13.3.
I have reported the problem to developer.apple.com/contact 24 hours ago, but have not received any valuable response yet.
Thank you very much. I will attach the previews-diagnostics.zip to FB10118238.
Thanks for the quick reply! The information you provided was very helpful to me.
Thanks for providing the information too! I've tried a lot of different combinations, but haven't found a pattern yet. Also haven't found a specific problem from Microsoft's SPM package. I'll come back later when I have a follow-up update :)
Uploaded previews-diagnostics to FB10118238. (The attachment is not shown in the Feedback Assistant, so I'm not sure if it was uploaded successfully. 🤔)
That's great! Thanks!