Update:

So we now have a github project (with all Catalina-related issues and PRs) and a wiki page to track Flutter support of Catalina.

Issues

1. Can't produce 32-bit armv7 binaries from a 64-bit environment #22598
2. VersionCheckError during flutter upgrade on macOS 10.15 beta (Catalina) #33890
3. Issues when using macos 10.15 & ios 13 #33909
4. flutter build apk - Fail on OSX Catalina #35018
5. macOS 10.15 beta error related to analysis_server.dart.snapshot #36114
6. Build release APK, found 'ProcessException: Bad CPU type in executable' error #36172
7. On macOS Catalina unsigned binaries blocked by Gatekeeper e.g. kernel-service.dart.snapshot, analysis_server.dart.snapshot #36714
8. Cocoapod path broken by upgrading macOS #36786
9. Xcode beta 11 requires adding signing certificate to each new flutter project #36788
10. Update "Getting Started" path setup to support zsh shell (macOS Catalina support) website#2856
11. Update "iOS Setup" page to reflect Xcode 11 UI update website#2857

Already ~1% of Flutter users are on Catalina.

There are a few known issues on Catalina (which are in various states of fixing), but no central location for tracking support of such.

I'm creating this bug to make sure support of Catalina is appropriately scheduled and executed on in time for Catalina's expected release later this year.

@cbracken can you please find the appropriate owner for chasing this?

I would like two things:

1. An owner/driver for this bug.
2. A wiki page (or some other reference, maybe even this bug?) with a set of known issues for Catalina so that those trying Flutter on Catalina can find the right resources.

Thanks.