Firebase Image Path Issue: Visualization Error After Successful Upload

[ambience-kim]

Can we access your project?

• [X] I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Expected Behavior

Photos uploaded to firebase should be displayed normally.

Steps to Reproduce

Please refer to the attached video.

https://github.com/user-attachments/assets/aa74a71c-22dd-410f-b7ac-3cafd6bb0979

Reproducible from Blank

• [ ] The steps to reproduce above start from a blank project.

Bug Report Code (Required)

I don't see the "Get Bug Report Code" menu in the widget tree. Please refer to the image for additional information.

Visual documentation

bug_report_20241026.pdf

Environment

- FlutterFlow version: latest version (update today)
- Platform: macOS, Desktop App
- Browser name and version: Chrome version 130.0.6723.59(official build) (x86_64)
- Operating system and version affected: macOS Venture 13.7

Additional Information

[Luca-Stoll]

Same problem here! Display of firebase image results in error "object progress event".

[Alezanello]

Hello!

Just to confirm, is this issue only occurring in Test Mode? Are Run Mode, Local Run, or any other tests working as expected?

[Luca-Stoll]

For me personally the error just vanished yesterday. I dont know why it was there and why its gone again (bc I did not change anything), but i have no issues with this anymore.

[ambience-kim]

1. Test Results

• Unfortunately, I am still experiencing this issue in test mode.
• I tested this issue by deploying it on both the web environment and the Android app (apk). Additionally, no issues were observed in either the web or Android environments.

2. My Assumptions

If my memory is correct, this issue began occurring after I changed the Firebase settings as follows:

• When initially configuring Firebase, I set the Firestore server location to asia-northeast3 (Seoul).

• For Storage, I chose the "Default" location, which displayed as asia-northeast3 (Seoul) on the screen.

• As a result, I also chose the "Default" location for the Cloud Function server. (At that time, the Default location wasn’t displayed on the screen, but I assumed it to be asia-northeast3 (Seoul).)

• However, I noticed the API response time was slower than expected. After verifying the API server location, I discovered that the Default location for Cloud Functions was us-central1, not asia-northeast3 (Seoul).

• To resolve this, I reviewed the Firebase settings and found that I could change the Cloud Function region to asia-northeast3 (Seoul), so I made the change.

• However, changing the region only updated the location for functions called through Private APIs after redeployment. For other functions (Push Notifications, Delete User Reference, etc.), deployment errors occurred, and their locations did not change.

• Therefore, I reverted the Cloud Function server location back to the Default setting.

3. Additional Testing

• Created a new project in FF + connected it to a new Firebase project ==> No issues.
• Created a new project in FF + connected it to the Firebase project with the issue ==> No issues.
• Based on this, I believe the issue is related to Firebase settings in FF.

[ambience-kim]

@Alezanello Please let me know if there’s any information I can provide to help resolve this issue. I’ll be happy to run additional tests and share the results with you.

[ambience-kim]

@Alezanello I am sharing the results of my tests up to today.

Test Mode

• Image does not display (shows an Object ProgressEvent)

Run Mode

• Image does not display (simply not visible)

Deploy (Web)

• No issues

Deploy (Android)

• No issues

[ambience-kim]

@Alezanello Just as a note, I had completed the CORS settings in Firestore previously.

[tyler4i234]

Are you still experiencing this issue, I having the same problem. If you fixed it i would love to know what you did!

[ambience-kim]

@tyler4i234

I am still experiencing this issue. I created a new project in Firebase yesterday to test it, but the problem persists.

The only solution I've found so far is to create an entirely new project in FF and connect it to a new project in Firebase. However, this would mean giving up everything I've developed so far, so it's not an option.

[tyler4i234]

@ambience-kim, this problem really sucks. My project was working just fine and suddenly this is issue occured. This has to be a bug from the new update right?

[ambience-kim]

@tyler4i234

To determine whether this issue is a bug or not, I believe we first need to establish a definition of what constitutes a bug. That's why I asked ChatGPT the following questions:

I believe that the FF team would reach the same conclusion.