DYDL error for iOS app on mac running on Big Sur archived with Xcode 13.3 RC

Think I'm running into a similar issue with an iOS app with an iOS 14 minimum target built with Xcode 13.3. App runs fine on iOS15, crashes with a similar error on iOS 14

Same thing is happening to us (with iOS 14), did you find a solution?

Having the same problem. My app will launch "tethered" from Xcode on iOS 14 but will not launch from SpringBoard. Also inspected binary with otool, everything looks good. This appears to be due to the following change from the Xcode 13.3 release notes: "The new chained fixups format is the default linking method when targeting macOS 11 or later, iOS 13.4 or later, watchOS 7.0 or later, and tvOS 14.0 or later. This new format results in smaller LINKEDIT segments in binaries. When targeting earlier operating system releases, the linker continues to generate the traditional opcode format in LINKEDIT for fixups, rebases, and binds. (85572905)". I wonder if there is a way to disable this new chained fixups format as a temporary fix.

xcrun dyld_info -fixup_chains /path/to/Framework.framework/Framework also reports this issue "chained fixups, seg_count exceeds number of segments" so it seems like something is corrupted in the dynamic linking information of the binary.

Following a hunch that I got from reading info on this related issue https://forums.swift.org/t/async-await-crash-on-ios14-with-xcode-13-2-1/54541/48, I disabled the "enable bitcode" build setting for my framework (it was already disabled for my app, so this isn't a problem - unfortunately bitcode really should be enabled, but this might be a temporary fix while we wait for an official one). I hypothesize that disabling bitcode altogether makes Xcode not put any bitcode segment in the binary, which fixes the seg_count issue (the cause of which, according to the swift.org link is that Xcode stripped the bitcode segment but didn't update the seg_count properly).

You can temporarily mitigate this issue (or at least I could) by disabling the new chained fixups link method that was enabled per this change in the Xcode 13.3 release notes:

The new chained fixups format is the default linking method when targeting macOS 11 or later, iOS 13.4 or later, watchOS 7.0 or later, and tvOS 14.0 or later. This new format results in smaller LINKEDIT segments in binaries. When targeting earlier operating system releases, the linker continues to generate the traditional opcode format in LINKEDIT for fixups, rebases, and binds. (85572905)

To disable the chained fixups, go to the "Other Linker Flags" build setting in Xcode and add two in the following order: -Xlinker -no_fixup_chains. (It's surprising to me that you need -Xlinker here but I got errors without it).

This should be viewed as a temporary workaround, because the chained fixups is a legitimate improvement to binary size and build time. Ideally Apple will correct this so that we can leverage that improvement on older versions of iOS like they seem to have intended.

The issue is that SomeFramework.framework was built with embedded bitcode (which is stored in a special segment), then the bit-code was removed. A bug in the bitcode removal tool is leaving the segment counts askew. The work around is to change the build settings such that "Enable Bitcode = No" for SomeFramework.framework (or more generally, disable bitcode everywhere in the app).

👋 Hi! My team hit the same issue with a build using Xcode 13.3. It only impact some users so it was very tough to figure out what was going on. Thanks to this answer, we were able to solve the issue by disabling Bitcode. Is this bug in the bitcode removal tool something we'll need to wait until the next version of Xcode to be fix, or is this something Apple will fix on their side? Is there any way that we will know when we can enable Bitcode again? Thanks!

the issues where resolved with Xcode 13.3.1