forked from flutter/flutter
-
Notifications
You must be signed in to change notification settings - Fork 1
State of Catalina Support
Ray Rischpater, KF6GPE edited this page Oct 10, 2019
·
13 revisions
Currently all known issues with using Flutter on macOS Catalina have been resolved and are part of the 1.9 release. If you are experiencing an issue not listed below that regressed with macOS Catalina, please file a new issue with "Catalina" in the title.
- [Xcode] Cannot build 32-bit APK on XCode >= 10 flutter #36114 Dart #36839. Fixed in flutter #37445 v1.8.4.
- Cocoapod path broken by upgrading system ruby version #36786 User intervention required to manually reinstall cocoapods via
sudo gem install cocoapods
,flutter doctor
copy was updated to reflect this in flutter #38560. - [Xcode] For each flutter app that I tried to run on an iOS device, I had to add my signing certificate in XCode #36788. Fixed in flutter #37733 v1.9.0.
- Gatekeeper preventing “kernel-service.dart.snapshot” from executing #36714. Fixed Dart ec2d06d4 and by signing & notarizing binaries as of v1.9.1. Note: currently only published versions are signed & notarized as the CI process is updated. Soon every commit on master should be signed & notarized.
Members of the Flutter team are working to bring full macOS Catalina support to Flutter. Work is being track on the GitHub project Flutter on macOS Catalina Support. In the mean time, we know that some of you have wanted to use the macOS Catalina betas with Flutter. Here’s christopherfujino’s step-by-step diary of what he’s experienced getting it working, which is helping inform the team’s work as to what’s necessary.
- This was on a new Mac Mini, right from the Apple Store
- Upgraded OS to Catalina preview, via https://www.apple.com/macos/catalina-preview/
- On macOS Catalina v10.15 Beta (19A512f), XCode Beta 11.0
- Using iterm2
- Downloaded stable flutter sdk from flutter.dev, v1.7.8+hotfix.3
- OS X prompts if iterm2 should be allowed access to
$HOME/Downloads
- When I enter the command
flutter/bin/flutter doctor
, OS X says “dart” can’t be opened because it was not downloaded from the App Store- After going to Settings -> Security & Privacy -> Open Anyway, I get another dialog:
dart
is a Unix app downloaded from the Internet. Are you sure you want to open it? - On clicking “open”, a new “Terminal” window was opened, and then it executes just
dart
, without any arguments, and then the terminal session exits.
- After going to Settings -> Security & Privacy -> Open Anyway, I get another dialog:
- When I re-issue the same command, “
flutter/bin/flutter doctor
”, this time the actual flutter tool is run, however a new dialog is opened: “kernel-service.dart.snapshot” can’t be opened because Apple cannot check it for malicious software. 3. When I go to Settings -> Security & Privacy -> Open Anyway, nothing happens. The text next to the button says:kernel-service.dart.snapshot
was blocked from opening because it is not from an identified developer. Re-running the command results in no change. - Trying to switch channels failed with:
flutter@macN1 flutter % bin/flutter channel master
Switching to flutter channel 'master'...
../../third_party/dart/runtime/bin/snapshot_utils.cc: 149: error: Failed to memory map snapshot: /Users/flutter/flutter/bin/cache/dart-sdk/bin/snapshots/kernel-service.dart.snapshot version=2.4.0 (Wed Jun 19 11:53:45 2019 +0200) on "macos_x64"
thread=5891, isolate=(null)(0x0)
pc 0x000000010bd945d5 fp 0x0000700006ee7c40 dart::Profiler::DumpStackTrace(void*)
pc 0x000000010badfdc2 fp 0x0000700006ee7d20 dart::Assert::Fail(char const*, ...)
pc 0x000000010bac2dfb fp 0x0000700006ee7dd0 dart::bin::Snapshot::TryReadAppSnapshot(char const*)
pc 0x000000010bac7eea fp 0x0000700006ee7e50 dart::bin::CreateIsolateAndSetup(char const*, char const*, char const*, char const*, Dart_IsolateFlags*, void*, char**)
pc 0x000000010bcdba48 fp 0x0000700006ee7f00 dart::RunKernelTask::Run()
pc 0x000000010be36a0d fp 0x0000700006ee7f30 dart::ThreadPool::Worker::Loop()
pc 0x000000010be36880 fp 0x0000700006ee7f70 dart::ThreadPool::Worker::Main(unsigned long)
pc 0x000000010bd90fc1 fp 0x0000700006ee7fb0 dart::ThreadStart(void*)
pc 0x00007fff73470cce fp 0x0000700006ee7fd0 _pthread_start
pc 0x00007fff7346d72b fp 0x0000700006ee7ff0 thread_start
-- End of DumpStackTrace
bin/flutter: line 183: 8210 Abort trap: 6 "$DART" --packages="$FLUTTER_TOOLS_DIR/.packages" $FLUTTER_TOOL_ARGS "$SNAPSHOT_PATH" "$@"
- Following this article and this comment, I disabled Gatekeeper globally, so that binaries can execute without being signed. Now flutter doctor no longer throws the dialog about “kernel-service.dart.snapshot” being unsigned. I was also able to successfully switch channels to master. Issue
- Under “flutter doctor” (FlutterValidator), “Downloaded executables cannot execute on host”. Issue
- We will have to update website documentation on updating path to reflect that Catalina will default to zsh. I updated my path in $HOME/.zshrc. Issue
- I don’t know how to install xcode. Tried the app store, I’m getting weird hits, including tutorials and xcode plugins, but I don’t see an actual xcode install...so it turns out the App Store version of Xcode doesn’t support Catalina. I needed to install the beta version from https://developer.apple.com/download
- Even after installing the Xcode beta, flutter doctor can’t detect it. The instructions “sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer” don’t work because xcode isn’t at that location. Fixed: .app file was in $HOME/Downloads/
- Cocoapods not detected, looks like this issue. Fixed with “sudo gem install -n /usr/local/bin cocoapods”. Ran “pod setup” and cocoapods support detected. Issue
- With ios 13 simulator, issued “flutter run”, it worked.
- Attempted to run on ipod touch in debug:
- No valid code signing certs
- Following instructions, “open ios/Runner.xcworkspace” -> Xcode
- In Xcode 11.0 beta 4, the signing interface is no longer under “General”, but in its own category, “Signing & Capabilities” Issue
- Re-running “flutter run”, hit this issue, however it doesn’t seem Catalina-dependent. “Flutter clean” fixed it.
- It seems like for each new Flutter app to be run on an iOS device, the cert needs to be added in Xcode. Issue
- Attempted to run on ipod touch in release:
- Successful
- Downloaded Android Studio/SDK
- Intel HAXM installer was blocked by Gatekeeper
- “Flutter run” successful on emulator
- Attempting to run on LG G7 ThinQ in debug:
- Successful
- Attempting to run on LG G7 ThinQ in release:
- Successful
- Run devicelab integration_ui_ios.dart test, passes
- Build APK
- Home of the Wiki
- Roadmap
- API Reference (stable)
- API Reference (master)
- Glossary
- Contributor Guide
- Chat on Discord
- Code of Conduct
- Issue triage reports
- Our Values
- Tree hygiene
- Issue hygiene and Triage
- Style guide for Flutter repo
- Project teams
- Contributor access
- What should I work on?
- Running and writing tests
- Release process
- Rolling Dart
- Manual Engine Roll with Breaking Commits
- Updating Material Design Fonts & Icons
- Postmortems
- Setting up the Framework development environment
- The Framework architecture
- The flutter tool
- API Docs code block generation
- Running examples
- Using the Dart analyzer
- The flutter run variants
- Test coverage for package:flutter
- Writing a golden-file test for package:flutter
- Setting up the Engine development environment
- Compiling the engine
- Debugging the engine
- Using Sanitizers with the Flutter Engine
- Testing the engine
- The Engine architecture
- Flutter's modes
- Engine disk footprint
- Comparing AOT Snapshot Sizes
- Custom Flutter engine embedders
- Custom Flutter Engine Embedding in AOT Mode
- Flutter engine operation in AOT Mode
- Engine-specific Service Protocol extensions
- Crashes
- Supporting legacy platforms
- Metal on iOS FAQ
- Engine Clang Tidy Linter
- Why we have a separate engine repo
- Reduce Flutter engine size with MLGO
- Setting up the Plugins development environment
- Setting up the Packages development environment
- Plugins and Packages repository structure
- Plugin Tests
- Contributing to Plugins and Packages
- Releasing a Plugin or Package
- Unexpected Plugins and Packages failures