添加-ObjC链接器标志后真机出现arm64重复符号错误求助

Hey there, I totally get how frustrating this duplicate symbols roadblock is—especially when you’ve already tried all the usual fixes and can’t dig into source code to clean up duplicates. Let’s focus on narrowing that -ObjC flag to only the frameworks that actually need it, so you can avoid the global linker chaos causing your arm64 errors.

The global -ObjC flag in Other Linker Flags tells the linker to load every Objective-C class and category across all your linked frameworks. That’s why you’re seeing duplicate symbols on arm64—multiple frameworks are defining the same symbols, and the linker is pulling all of them in. Instead, we can restrict this behavior to just the frameworks that require -ObjC (usually ones that rely on category extensions to work properly).

Option 1: Use -force_load for Individual Frameworks #

This is the most precise approach. The -force_load flag forces the linker to load all symbols from a specific framework binary, which achieves the same goal as -ObjC but only for that single framework. Here’s how to set it up:

• Open your project’s Build Settings and search for Other Linker Flags (OTHER_LDFLAGS).
• Remove the global -ObjC entry if you have it.
• Add a new entry formatted like this:

  -force_load $(PROJECT_DIR)/Path/To/YourFramework.framework/YourFramework
  

  Replace $(PROJECT_DIR)/Path/To/YourFramework.framework/YourFramework with the actual relative path to your framework’s inner executable. For example, if your framework is in a Frameworks folder at the root of your project, it might look like $(SRCROOT)/Frameworks/MySDK.framework/MySDK.
• If you have multiple frameworks that need this treatment, add a separate -force_load line for each one.

Option 2: Quick Pre-Flight Checks #

Just to cover all bases, double-check these even if you’ve done them before:

• Ensure you’re only importing .h header files in your code, never .m files (even accidental imports can trigger duplicate symbols).
• Confirm no third-party frameworks you’re linking include duplicate static libraries or symbol definitions (common in closed-source SDKs that bundle dependencies).
• Clean your build folder (Cmd+Shift+K) and delete derived data before rebuilding—cached build artifacts can sometimes cause false duplicate symbol errors.

Why This Works #

-force_load targets exactly the framework that needs category/class loading, instead of telling the linker to scan every framework in your project. This cuts down on the chance of overlapping symbols being pulled in from unrelated frameworks, which is the root cause of your arm64 duplicate symbol errors.

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