Getting your iOS Flutter builds to work again.
If you’re like me, you’ve been enjoying using Flutter to make some really great apps lately. One of the things about using such a cutting edge framework is that you’re bound to encounter some potentially weird issues…without knowing exactly how to fix it.
I just spent 4 hours on the domain/default
pair issue. In your build log it looks like this:
/Users/user/Documents/strutsin/build/ios/Release-iphoneos/Runner.app/Frameworks/App.framework/App: signed bundle with Mach-O universal (arm64) [io.flutter.flutter.app]
/Users/user/Documents/strutsin/build/ios/Release-iphoneos/Runner.app/Frameworks/Flutter.framework/Flutter: signed bundle with Mach-O universal (armv7 x86_64 arm64) [io.flutter.flutter]
2020-08-14 00:02:17.303 defaults[21292:126352]
The domain/default pair of (/Users/user/Documents/strutsin/build/ios/Release-iphoneos/Runner.app/Frameworks/App.framework/flutter_assets/ios/Flutter/App.framework/Info.plist, CFBundleExecutable) does not
exist
fatal error: lipo: can't map input file: /Users/user/Documents/strutsin/build/ios/Release-iphoneos/Runner.app/Frameworks/App.framework/flutter_assets/ios/Flutter/App.framework/ (Invalid argument)
fatal error: lipo: can't map input file: /Users/user/Documents/strutsin/build/ios/Release-iphoneos/Runner.app/Frameworks/App.framework/flutter_assets/ios/Flutter/App.framework/ (Invalid argument)
Failed to extract arm64 for /Users/user/Documents/strutsin/build/ios/Release-iphoneos/Runner.app/Frameworks/App.framework/flutter_assets/ios/Flutter/App.framework/. Running lipo -info:
fatal error: lipo: can't map input file: /Users/user/Documents/strutsin/build/ios/Release-iphoneos/Runner.app/Frameworks/App.framework/flutter_assets/ios/Flutter/App.framework/ (Invalid argument)
Command PhaseScriptExecution failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
#flutter #mobile-apps #web-development #developer