ListView selective rendering of DB Documents and Error serializing doc errors on ListView

[DayneLinx]

Has your issue been reported?

• I have searched the existing issues and confirm it has not been reported.
• 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

I have linked my firebase DB to a list view widget and for a couple of days it would render all records from the database. After a these couple of days and with no changes made with either tool it would start to generate a subset of the records randomly and no images that accompanied them. Now this is even more bizarre in that all the records can be seen and are accurate in the MANAGE CONTENT view and including the images. Now, I am assuming if there was a problem with the data it would also not render in that view also. I have used the developer tools both Edge and Opera and I am getting the same errors when rendering the ListView. (Images Attached).

Debugging Window Errors

Error serializing doc
EXCEPTION CAUGHT BY IMAGE RESOURCE SERVICE
No images rendered from the DB (Object Event)

Expected Behavior

I link my Firebase DB to a ListView widget and expected the documents to be rendered within the ListView. This worked for a couple of days only. When I tap on a row i expect to be taken to a details page rendered with all the relevant database fields attached to widgets

Steps To Reproduce

1. Create new page
2. Add ListView widget
3. Add Backend Query
4. Query Type : Query Collection
5. Select my ‘Beaches’ collection
6. Initiate Run Mode
7. Beaches Records are rendered in the list
8. Return to the editing interface
9. Select a row in the list
10. Select Define Action
11. On Tap - Navigate to ‘Beach Detail Page’
12. Create a parameter ‘beachDetails’
13. Available Options: Get Document Property - Document Properties: Reference
14. Open my ‘Beach Details’ Page
15. Select a Column view to add a backend query to
16. Add Backend query - Document from Reference - Collection: Beaches - Select the ‘beachDetails’ Reference
17. Select the ‘Beach Name’ text widget
18. Select - Set From Variable - Beaches Document - Beach Name
19. Run the App
20. ListView renders the list of documents with selective rendering and not rendering all of the records
21. When I tap on a row I get a Red screen of death - (Screenshots included)

Bug Report Code

ITFfkuflwItIsdtK0L6ILMFsjiMXHG0cTeUzlO1hdwwbI+PrB4kUPPSkQE5CWOqHdFBqB2KWpEwepfz5uezLMfkVOQ2qQbpi+s9XUxDgfGqhbLq4Ec2OdH9TL+VPI32B1sOokx15HMhiLlpg62WUI+6Qa3qCf9qOYwx5e6fDbOY=

Context

I cannot run the app and make progress building my details page or ListView accurately

Additional info

No response

Environment

- Version of FlutterFlow used: **3.7.3 - Previous versions had the same issue**
- Platform (e.g. Web, MacOS Desktop): **Web**
- Browser name and version: Edge: **110.0.1587.63 (Official build) (x86_64)** Opera: **95.0.4635.46 (x86_64)**
- Operating system and version (desktop or mobile): **macOS Big Sur** **macOS Ventura**

[hariprasadms]

Hi @DayneLinx - Thanks for sharing this issue. Looking at the below error, I suspect, data type in the document is changed.
Can you please double check recent changes you made? Use project history snapshots to revert back to previous version of the app and see how it works.

[DayneLinx]

I will do, but all that changed really was the version of Flutterflow. I will let you know the results later. Thanks for getting back to me.

[DayneLinx]

Same thing happened again. Some selected images have now appeared and I removed a DB entry that was correct and it still gets a red screen when tapping a row.

[DayneLinx]

I am using ROWY too but I don't see how that would affect the rendering.

[wenkaifan0720]

Hi @DayneLinx. The renderflex overflow exceptions can be all disregarded as it is just telling you some widgets do not fit. The unexpected null value is the real issue, and seems to be caused by the BeachDetailsRC2 page, in which you set a page parameter called beachDetails of type document reference. You don't seem to set this page parameter now and it is causing issue.

[github-actions]

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.