We're also running into an issue that appears to be related to Xcode 16.0, the primary issue is that Firebase Crashlytics has missing dSYMs. However, during dSYM upload / processing, it finds and successfully uploads a dSYM: In the Xcode 16.0 console I see the same message as mentioned above: "warning: (arm64) /Users/user/Library/Developer/Xcode/DerivedData/SomeApp-dih...wzn/Build/Products/Debug-iphonesimulator/SomeApp.app/SomeApp empty dSYM file detected, dSYM was created with an executable with no debug info." I tried changing the build settings for our targets, directly in Xcode's build settings as well as using externalized configuration (.xcconfig). Enabled for debug and release: DEBUG_INFORMATION_FORMAT = dwarf-with-dsym DEBUG_INFORMATION_VERSION = compiler-default CLANG_DEBUG_INFORMATION_LEVEL = default For debug: COPY_PHASE_STRIP = NO For release: COPY_PHASE_STRIP = YES Snippet from the automated build log: 14:08:19 14:08:19 Platform: ios 14:08:19 14:08:19 DSYM Paths: ["/Users/.../SomeApp.xcarchive/dSYMs/SomeApp.app.dSYM"] 14:08:19 14:08:19 14:08:19 14:08:19 Inspecting next path: /Users/.../SomeApp.xcarchive/dSYMs/SomeApp.app.dSYM 14:08:19 14:08:19 Found dSYM at path: /Users/.../SomeApp.xcarchive/dSYMs/SomeApp.app.dSYM 14:08:19 14:08:19 Begin processing dSYM at /Users/.../SomeApp.xcarchive/dSYMs/SomeApp.app.dSYM 14:08:19 14:08:19 Zipping csym for uuid c2c....8443c, architecture: arm64 14:08:19 14:08:19 Zipping csym succeeded for uuid c2c....8443c, architecture arm64... getting compressed data 14:08:19 14:08:19 Deleting file at path: /var/folders/20/.../T/arm64-c2c....8443c.csym 14:08:19 14:08:19 Deleted file at path /var/folders/20/.../T/arm64-c2c....8443c.csym 14:08:19 14:08:19 Deleting file at path: /var/folders/20/.../T/some.zip 14:08:19 14:08:19 Deleted file at path /var/folders/20/.../T/some.zip 14:08:19 14:08:19 Uploading cSYM to https://firebasecrashlyticssymbols.googleapis.com/v1/project/-/app/1:123456:ios:9e...c4/upload/native/c2c....8443c 14:08:19 14:08:19 Uploading cSYM for uuid c2c....8443c, architecture arm64 14:08:19 14:08:19 Successfully submitted symbols for architecture arm64 with UUID c2c....8443c in dSYM: /Users/.../SomeApp.xcarchive/dSYMs/SomeApp.app.dSYM I was not yet able to check the dSYM on the build node(s), but I am suspecting this is an empty dSYM like Xcode is reporting locally. Note that unlike some reports above we also do not experience a crash (so that seems like it is unrelated). Probably unrelated, but we use cocoapods for dependency management. It looks like the Firebase issue of missing dSYMs and the empty dSYM message in Xcode coincided with moving from Xcode 15.4 to Xcode 16.0 I tried Xcode 16.1 beta 3 (16B5029d) but I am still seeing the "empty dSYM file detected, dSYM was created with an executable with no debug info." message.

@DTS Engineer, Ed, there is already a thread for "warning: (arm64) /Users/user/Library/Developer/Xcode/DerivedData/SomeApp-dih...wzn/Build/Products/Debug-iphonesimulator/SomeApp.app/SomeApp empty dSYM file detected, dSYM was created with an executable with no debug info." https://developer.apple.com/forums/thread/764301 In that thread you point to this thread :)

Unfortunately not, @jakeackermangreenlight . The challenge is that a solution needs to involve IT / Security. I find it mind boggling that CrowdStrike, a company use by the largest enterprises (as was clearly demonstrated in yesterday’s global outage), somehow isn‘t able to handle legit Xcode distributions and compilers. Endpoint protection is fine, but it shouldn’t interfere that much with your day to day work by consuming significant resources.

Update: we managed to fix the issue on our end by moving the 'Embed Frameworks' build phase above the 'Run script' build phase(s).

We're seeing the same error, but we don't change DSTROOT. We have 2 frameworks in our workspace, where framework a links to and depends on framework b (Always Used / Do Not Embed) and the host app depends and embeds and signs both framework a and b (Always Used / Embed & Sign). This works fine in Xcode 14.3.1 but causes the Cycle inside ...; building could produce unreliable results error in Xcode 15.0 beta 1.

Thank you, I filed feedback: FB11934338

Yeah, I only experience the issue when running in iOS 16.1 Simulator. On device it seems to work as expected.