Hi all, I've been seeing this issue a couple times in the forum. This is happening because of the upgrade to Flutter 3.32.4 yesterday. One of the breaking changes (as noted in the migration guide), is the removal the html renderer for web. In order to fix the CORS issues, you'll need to configure CORS in Firebase. I spoke with a member of our support team, and here's what worked for some users the support team has spoken with:

Follow steps 1-3 in the documentation here: https://docs.flutterflow.io/configuring-cors-for-firebase-storage/

Then, create a cors.json file and upload it. Here's what the cors.json file can look like:

[\n    {\n     \"origin\": [\"*\"],\n     \"method\": [\"GET\"],\n     \"maxAgeSeconds\": 3600\n     }\n]

Note that this example is fully permissive. If you want to limit the valid origin domains you can add them to the \"origin\" field, ex. \"origin\": [\"allowed-origin.com\"],

Once you've created that file, upload it to your console:

To confirm that you have uploaded it correctly, you can run ls and you should see cors.json in there.

Once you've confirmed you have your cors.json file, run this command in the terminal:
gcloud storage buckets update gs://your-bucket-name --cors-file=cors.json

And then test from there. I hope this works for you! Please keep me posted.

Tagging you all so hopefully you see it :) Steve Hasib April Mullner Oliver Wittmann Wilsmann Keegan Dan Hostettler

Images not displaying in test mode