Apple New Added 26 October 2026

Xcode: SDK does not contain 'libarclite' at the path

Xcode 14.3 removed libarclite, the small library that let ARC code run on very old OS versions, so any target whose deployment target is below what current Xcode supports now fails to link. Your app target is usually fine. The culprit is a CocoaPods dependency whose podspec still declares iOS 8 or 9, which CocoaPods copies into the Pods project. It is very common in Flutter and React Native projects straight after an Xcode upgrade.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# Which deployment targets does the Pods project still use?
grep -o "IPHONEOS_DEPLOYMENT_TARGET = [0-9.]*" ios/Pods/Pods.xcodeproj/project.pbxproj | sort | uniq -c

# Raise them in a post_install hook in ios/Podfile
# platform :ios, '12.0'
# post_install do |installer|
#   installer.pods_project.targets.each do |target|
#     flutter_additional_ios_build_settings(target)   # Flutter projects only
#     target.build_configurations.each do |config|
#       config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
#     end
#   end
# end

cd ios && pod install && cd ..

# Long term: update the pod, newer releases usually fix their podspec
cd ios && pod outdated

How to diagnose Apple errors

macOS developer errors concentrate around three subsystems: the command line tools (xcrun and the active developer directory), the dynamic linker (dyld, library paths, and code signing), and Gatekeeper / notarisation. Apple Silicon added a fourth axis: architecture mismatches between arm64 and x86_64 binaries, which usually surface as confusing "library not loaded" or "bad CPU type" messages rather than as an explicit architecture error.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Check the active developer directory first with xcode-select -p. After every macOS or Xcode update this can point at a path that no longer exists, breaking git, compilers and package managers all at once.
For dyld errors, run otool -L /path/to/binary to list what it actually wants, then verify each path exists. DYLD_PRINT_LIBRARIES=1 shows the resolution order at runtime.
Confirm architecture with file /path/to/binary and uname -m. On Apple Silicon, a Rosetta shell reports x86_64 and will silently install the wrong Homebrew prefix.
Homebrew lives at /opt/homebrew on Apple Silicon and /usr/local on Intel. Permission errors under /usr/local on an M-series Mac almost always mean a Rosetta/native mix-up.
For Gatekeeper and notarisation, use spctl -a -vvv to assess a bundle and xcrun notarytool log to get the actual rejection reason. The submission status alone tells you nothing useful.

Tools worth reaching for

xcode-select -p
otool -L
codesign -dv --verbose=4
spctl -a -vvv
xcrun notarytool log

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

developer.apple.com guides.cocoapods.org

Related Apple errors

See all 20 Apple errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.