FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
130 stars 26 forks source link

Firebase Image Path Issue: Visualization Error After Successful Upload #4666

Open ambience-kim opened 3 weeks ago

ambience-kim commented 3 weeks ago

Can we access your project?

Current Behavior

image_01 image_02 image_03 image_04 image_05 image_06 image_07

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

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

스크린샷 2024-10-26 오후 12 06 53

Luca-Stoll commented 3 weeks ago

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

Alezanello commented 3 weeks ago

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 commented 3 weeks ago

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 commented 3 weeks ago

1. Test Results

2. My Assumptions

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

3. Additional Testing

ambience-kim commented 3 weeks ago

@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 commented 3 weeks ago

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

Test Mode

Run Mode

Deploy (Web)

Deploy (Android)

ambience-kim commented 3 weeks ago

@Alezanello Just as a note, I had completed the CORS settings in Firestore previously. 스크린샷 2024-11-01 오후 2 16 07

tyler4i234 commented 2 weeks ago

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 commented 2 weeks ago

@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 commented 2 weeks ago

@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 commented 2 weeks ago

@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: 스크린샷 2024-11-05 오전 11 31 44

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

ambience-kim commented 2 weeks ago

@Alezanello I raised this issue about two weeks ago, and I was wondering if you could share any updates on its progress.

As I mentioned before, I’m fully prepared to conduct any tests necessary to help resolve this issue, so please feel free to let me know if there’s anything your team needs from my side. I’d be happy to assist with anything.

tyler4i234 commented 1 week ago

@ambience-kim I found a solution that worked for me. You need to disable CanvasKit (beta) Render in App Settings > Web Deployment > General Information. After you turn that off reload everything and you should be fine.

rzambroni commented 2 days ago

Hi everyone,

Apologies for the delay in following up on this. We’re actively working to get up to speed. Were you able to resolve the issue by disabling the CanvasKit beta?

If the issue persists, would it be possible for you to share a blank project where the issue can be reproduced? Unfortunately, we haven’t been able to replicate it in our own test projects, and having your example would greatly help us troubleshoot more effectively and speed up the resolution process.

Thank you for your patience and understanding!