Skip to content
MappleCare Community ↗

MappleCare Community

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

Find answers from other Apple users or start a discussion about your device.

All Forum Rooms

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

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • November 14, 2026 at 11:46 pm #14861
    Richard Morris
    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 #256347721

    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?

    MacBook Air 13″ M3 (16GB) | Apple GSX Terminal | Thermal Camera Seek Compact | Hamburg, DE
    Apple Certified Service Technician (ACiT / ACSP) | "Verified Apple Discussions Archive"
    November 14, 2026 at 11:46 pm #14862
    Ethan Allen
    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.

    Apple Vision Pro (1TB) | Mac mini M4 Pro (48GB) | Studio Display | Philadelphia, PA
    Apple Certified Support Professional (ACSP) | visionOS Spatial Computing Developer
  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.