Xcode 10.2编译RealmSwift时CMD+R崩溃，CMD+U/Archive正常求助

Hey there, let's break down this issue and walk through the fixes that should get your project compiling again when deploying to the simulator in Xcode 10.2.

Understanding the Problem #

First, let's recap what you've already uncovered to make sure we're aligned:

• Your project works flawlessly in Xcode 10.1 (Swift 4)
• In all Xcode 10.2 variants (Beta 2, Beta 4, Release), deploying to the simulator (CMD+R) triggers a segmentation fault during RealmSwift compilation
• Running tests (CMD+U) and archiving work fine — only simulator deployment breaks
• The issue isn't tied to Swift version (happens with both 4 and 5)
• Isolating your Realm-dependent Data Module in a blank project works, so it's a conflict with your main project's configuration

Looking at the crash log, the failure happens during LLVM's Dominator Tree Construction pass while processing RealmSwift's LinkingObjects type — this points to a compiler toolchain bug in Xcode 10.2 triggered by specific build settings.

Step-by-Step Fixes #

1. Disable Thread Sanitizer (Most Likely Fix) #

Your compile command shows -sanitize=thread is enabled, and this is a known trigger for this exact crash in Xcode 10.2. Here's how to turn it off:

• Open your scheme editor: Product > Scheme > Edit Scheme
• Go to the Run tab, then the Diagnostics section
• Uncheck the Thread Sanitizer box
• Clean your build folder (CMD+Shift+K) and rebuild the project

This should resolve the segmentation fault immediately in most cases.

2. Update RealmSwift to a Compatible Version #

Realm addressed Xcode 10.2 compatibility issues in later releases of RealmSwift 3.x. Try updating to version 3.19.0 or newer (the latest stable 3.x release):

1. Update your Podfile:

   pod 'RealmSwift', '~> 3.19.0'
   

2. Run pod update RealmSwift in your terminal
3. Clean and rebuild your project

3. Workaround: Use Prebuilt Realm Frameworks #

If updating isn't feasible right now, you can switch to Realm's prebuilt frameworks instead of using CocoaPods:

• Download the latest prebuilt RealmSwift framework from Realm's official releases
• Remove the RealmSwift CocoaPods dependency from your Podfile, run pod deintegrate then pod install
• Add the downloaded framework to your project, link it to your targets, and ensure it's embedded correctly

4. Reset Build Cache & Derived Data #

Corrupted build artifacts can sometimes cause unexpected compiler crashes. Let's rule this out:

• Delete your Derived Data folder: ~/Library/Developer/Xcode/DerivedData
• Reset Xcode's build cache: File > Project Settings > Build Location > Advanced > Reset
• Reinstall your pods: pod deintegrate && pod install

Why This Happens #

The root cause is a bug in Xcode 10.2's Swift toolchain that fails to process RealmSwift's LinkingObjects implementation when certain sanitizers (like Thread Sanitizer) are enabled in combination with your main project's build settings. Since the issue doesn't occur in isolation or during non-simulator builds, it's a specific interaction between the compiler, Realm's code, and your project's configuration.

内容的提问来源于stack exchange，提问作者Isaac