@blasten @kf6gpe - we need to fix the certificate attached to download.flutter.io/download.flutter.dev. Looks like it's using the one for *.storage.googleapis.com, which triggers a bunch of warnings/errors over HTTPS.

+1. GCP storage only supports CNAME entries for custom domains, which doesn't allow HTTPS.
https://cloud.google.com/storage/docs/troubleshooting#https

If we think this is critical, then we might either need to migrate to Firebase hosting as suggested in the GCP storage doc or drop the custom domain and use https://storage.googleapis.com/download.flutter.io directly.

Would the setting up a load balancer option work out for us?

I think we should probably avoid firebase hosting for this - it will become tedious as we add more and more files (AFAIK it requires a complete local copy of your static assets to compare/upload - there's no way to just say "add these new assets").

If a load balancer doesn't work, I'd vote for just using the storage.googleapis.com domain directly. Will that have any negative impact on Chinese customers though?

any negative impact on Chinese customers though

Cannot speak for the future, but currently https://storage.googleapis.com/download.flutter.io works in China.

@blasten what would it take to just use storage.googleapis directly?

very easily.

Need to update docs as well https://flutter.dev/docs/development/add-to-app/android/project-setup#option-a---depend-on-the-android-archive-aar

Docs and sample updated.
flutter/website#3768
flutter/samples#355

This 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 -v and a minimal reproduction of the issue.