Skip to content
[Solved] How to fix Xcode Linker Error: ‘Undefined symbols for architecture arm64’ caused by Missing universal arm64 binary slice in legacy CocoaPods or precompiled dylib frameworks on MacBook Pro 16″ M3 MaxMappleCare Community ↗

[Solved] How to fix Xcode Linker Error: ‘Undefined symbols for architecture arm64’ caused by Missing universal arm64 binary slice in legacy CocoaPods or precompiled dylib frameworks on MacBook Pro 16″ M3 Max

Started by Daniel Crawford • November 17, 2026 at 5:03 pm • 1 Community Replies • 2 Participants

Home › Forums › Apple Silicon, Terminal & Developer Tools › [Solved] How to fix Xcode Linker Error: ‘Undefined symbols for architecture arm64’ caused by Missing universal arm64 binary slice in legacy CocoaPods or precompiled dylib frameworks on MacBook Pro 16″ M3 Max

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #70541
    Kullanıcı ProfiliDaniel Crawford
    Community Contributor
    Diagnostic Hardware Specs: MacBook Pro 16″ M3 Max (64GB) | OS Version: macOS Sonoma 14.7 + Xcode 16.0 | Archive Source: Apple Support Community #256506065

    I am running into a persistent issue on my MacBook Pro 16″ M3 Max (64GB) running macOS Sonoma 14.7 + Xcode 16.0.
    Whenever the machine encounters Missing universal arm64 binary slice in legacy CocoaPods or precompiled dylib frameworks, the following diagnostic log appears in Console:

    ld: symbol(s) not found for architecture arm64; clang: error: linker command failed with exit code 1 (use -v to see invocation)

    I verified that hardware connections are intact and tested across different power sources. What is the verified diagnostic procedure to permanently eliminate this symptom?

    Mac Studio M1 Max (32GB) | Dual Dell UltraSharp 4K | Logitech MX Master 3S | Auckland, NZ
    Product Designer & Design Systems Lead | "Verified Apple Discussions Archive"
    #70542
    Kullanıcı ProfiliOlivier Davies
    Community Contributor
    Apple Recommended / Verified Community Solution
    This canonical solution was verified and marked as solved in the Apple Support Community archive.

    Inspecting binary slices via lipo, updating dependency architecture flags, and cleaning derived data.

    Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:

    1. Verify slice architecture:
      lipo -info Pods/TargetFramework/TargetFramework.framework/TargetFramework
    2. In Xcode Build Settings, search for Excluded Architectures and ensure arm64 is NOT excluded for Any iOS/macOS SDK.
    3. Purge build cache:
      rm -rf ~/Library/Developer/Xcode/DerivedData/* && xcodebuild clean

    Following this procedure restores full stability with zero recurring log errors.

    iPhone 16 Pro Max (1TB) | Apple Watch Ultra 2 | Austin, TX
    Apple Certified Support Professional (ACSP) | Creative Pro Video Editor
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.