Environment
- google_mlkit_barcode_scanning: 0.14.2
- google_mlkit_commons: 0.11.1
- Xcode: 26.3 (Build 17C529)
- iOS SDK: 26.2
- Flutter: 3.41.4
- Platform: macOS (Apple Silicon)
Problem
When building with Xcode 26 for iOS 26+ simulators, the following transitive pods fail the arm64 architecture requirement:
The following target(s) do not support arm64 architecture, which is a requirement
for Apple Silicon iOS 26+ simulators:
- GoogleMLKit (transitive dependency of Flutter plugin google_mlkit_barcode_scanning)
- MLImage (transitive dependency of Flutter plugin google_mlkit_commons)
- MLKitBarcodeScanning (transitive dependency of Flutter plugin google_mlkit_barcode_scanning)
- MLKitCommon (transitive dependency of Flutter plugin google_mlkit_barcode_scanning)
- MLKitVision (transitive dependency of Flutter plugin google_mlkit_commons)
These are the upstream Google MLKit pods that this plugin depends on. The pods were built without arm64 simulator slices for iOS 26.
Steps to reproduce
- Install Xcode 26
- Create a Flutter project with
google_mlkit_barcode_scanning: ^0.14.2
- Run
flutter run targeting an iOS 26 simulator on Apple Silicon
Expected behavior
Build and run succeeds on iOS 26 simulators.
Notes
This is ultimately a Google MLKit pod issue. Once Google publishes updated pods with iOS 26 simulator support, bumping the pod version constraints in the podspec should resolve it.
Workaround
Build on Xcode 16.x, or target physical devices only.
Environment
Problem
When building with Xcode 26 for iOS 26+ simulators, the following transitive pods fail the arm64 architecture requirement:
These are the upstream Google MLKit pods that this plugin depends on. The pods were built without arm64 simulator slices for iOS 26.
Steps to reproduce
google_mlkit_barcode_scanning: ^0.14.2flutter runtargeting an iOS 26 simulator on Apple SiliconExpected behavior
Build and run succeeds on iOS 26 simulators.
Notes
This is ultimately a Google MLKit pod issue. Once Google publishes updated pods with iOS 26 simulator support, bumping the pod version constraints in the podspec should resolve it.
Workaround
Build on Xcode 16.x, or target physical devices only.