Description
After libavif was updated from 0.11.1 to 1.0.0 on CocoaPods, pod install generates a Pods.xcodeproj that Xcode cannot parse. The build fails with:
-[PBXShellScriptBuildPhase setSavedArchiveVersion:]: unrecognized selector sent to instance 0x600002718090
The project 'Pods' is damaged and cannot be opened. Examine the project file for invalid edits or unresolved source control conflicts.
Path: /Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj
This causes all Pod-based modules to be missing during compilation (e.g. no such module 'Expo'), making the project unbuildable.
Environment
- CocoaPods: 1.16.2
- Xcode: 26.0 (17A324) — also reproduced on Xcode 16.4 (16F6)
- macOS: Sequoia 15.6
- Ruby: 3.2
- Platform: EAS Build (Expo Application Services), but not Expo-specific — affects any CocoaPods project that depends on
libavif
Reproduction
- Create or use any iOS project with CocoaPods that transitively depends on
libavif (e.g. via SDWebImageAVIFCoder)
- Run
pod install — resolves libavif to 1.0.0
- Build the project with Xcode
- Xcode reports
Pods.xcodeproj is damaged and cannot be opened
Working version
Pinning libavif to 0.11.1 in the Podfile resolves the issue:
Description
After
libavifwas updated from0.11.1to1.0.0on CocoaPods,pod installgenerates aPods.xcodeprojthat Xcode cannot parse. The build fails with:This causes all Pod-based modules to be missing during compilation (e.g.
no such module 'Expo'), making the project unbuildable.Environment
libavifReproduction
libavif(e.g. viaSDWebImageAVIFCoder)pod install— resolveslibavifto1.0.0Pods.xcodeprojis damaged and cannot be openedWorking version
Pinning
libavifto0.11.1in the Podfile resolves the issue: