Repository navigation
library.rb:275: [BUG] Bus Error at 0x00000001042fc000 #99195
Copy link
Copy link
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work lista: buildBuilding flutter applications with the toolBuilding flutter applications with the toola: desktopRunning on desktopRunning on desktopa: first hourThe first hour of using FlutterThe first hour of using Flutterplatform-host-armBuilding on an ARM-based platformBuilding on an ARM-based platformplatform-iosiOS applications specificallyiOS applications specificallyplatform-macosBuilding on or for macOS specificallyBuilding on or for macOS specificallytoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
Activity
- addedtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.platform-macosBuilding on or for macOS specificallyBuilding on or for macOS specificallya: first hourThe first hour of using FlutterThe first hour of using Fluttera: desktopRunning on desktopRunning on desktopa: buildBuilding flutter applications with the toolBuilding flutter applications with the toolP2Important issues not at the top of the work listImportant issues not at the top of the work list
on Feb 26, 2022 - addedplatform-iosiOS applications specificallyiOS applications specificallyplatform-host-armBuilding on an ARM-based platformBuilding on an ARM-based platform
on Apr 13, 2022 I hit this today and followed instructions from https://stackoverflow.com/questions/69867593/flutter-run-crash-on-ios-error-running-pod-install
To do:
sudo arch -x86_64 gem install ffi arch -x86_64 pod installin the "ios" folder, and then
flutter build iosworked just fine. :)It also may be Google-mac specific? I don't know if we have a different ruby than default on these machines (I know we used to have a non-standard python which sometimes caused problems).
eseidel-macbookpro3% flutter --version Flutter 2.13.0-0.0.pre.483 • channel master • https://github.com/flutter/flutter.git Framework • revision b086473769 (30 hours ago) • 2022-04-11 20:19:09 +0100 Engine • revision 32a2cab5d1 Tools • Dart 2.18.0 (build 2.18.0-10.0.dev) • DevTools 2.12.2 eseidel-macbookpro3% ruby --version ruby 2.6.8p205 (2021-07-07 revision 67951) [universal.arm64e-darwin21] eseidel-macbookpro3% gem --version 3.0.3.1 eseidel-macbookpro3% pod --version 1.11.3Reacted by Miguel de Sousa and RobertBoutenThis thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on May 5, 2022
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work lista: buildBuilding flutter applications with the toolBuilding flutter applications with the toola: desktopRunning on desktopRunning on desktopa: first hourThe first hour of using FlutterThe first hour of using Flutterplatform-host-armBuilding on an ARM-based platformBuilding on an ARM-based platformplatform-iosiOS applications specificallyiOS applications specificallyplatform-macosBuilding on or for macOS specificallyBuilding on or for macOS specificallytoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Steps to reproduce
flutter create --platforms=macos .flutter config --enable-macos-desktopsudo gem install cocoapods(as instructed by https://guides.cocoapods.org/using/getting-started.html#installation, which is pointed to byflutter doctor)flutter run -d macosExpected behavior
You expect the app to run (it's out of date and has errors after running, but it still should be able to run).
Actual behavior
You get an error building. The main error is:
Googling for that error will eventually lead you to CocoaPods/CocoaPods#10723 (comment)
So then, you run:
But when you run the app again, you still get the same error.
It turns out that you can get it working by applying the following patch to flutter_tools:
... but presumably we shouldn't be unconditionally running that.