List View / Grid View not showing anything when placed inside of a container

List and Grid Views do not show anything when placed inside of a container. This worked fine yesterday, now it is broken.

  • I have already tried refreshing and importing from json
  • Tested in both Firefox and Chromium based browsers
  • Tested with data containing 1 or more objects

Picture 1. List View is not inside of any container. 2 items are properly being displayed

Picture 2. List View is inside of a tabbed container. No items are shown

Picture 3. List View is inside of a regular container. No items are shown

Picture 4. List View clearly has items still as shown in tree, but no components are displayed when nested in a container.

Screenshot 2024-08-21 at 10-47-01 Age Better Editor Retool

Here is a loom video showing that it also is broken when using the Split Frame...

1 Like

I'm also having the same issue, some My TextInputs have also disappeared,

If you look at this picture ReviewNameFilter should be above ReviewNameListBox but it is no longer visible

1 Like

Managed to fix it by turning off WidgetGrid, seems to be an issue with the new features

2 Likes

I have exactly the same issue since yesterday.

Items inside all of my listview components are not showing no matter what the source is array or database. Even standard template (AI Chat) is not displaying messages inside thelistview correctly.

My listviews are inside different containers and few of them are in drawer.


This fixed it for me, well done.

It worked, thank you!

For anyone else struggling to turn this off. It's in the bottom left corner of the app.

image

Hi folks! I'm glad to see you found a temporary solution :pray:

We are investigating internally as well for a fix so that you can still use widget grid

Anyone else experiencing a bug where listViews aren't displaying data properly? I'm experiencing this in multiple apps.

They were all working fine until this morning, when they (apparently randomly) just stopped displaying any info. Instead, I just see the option to "Add components", when I can clearly see from the component tree in the left sidebar that all the components I've previously added (e.g. select boxes, radio groups etc.) are still present in the listView and all have valid values, but just are not being displayed. Here are the screenshots.

I haven't changed anything that would affect any listView - the data sources for the various list views are working properly and returning results exactly as they were last night, when everything was functional. In fact, I've tried deliberately changing the queries to be wrong, which causes the listView to have a red border to indicate that there's something wrong. When I revert my queries back to their original state, this border goes away, indicating that the data is in the correct format etc.

I'm setting the value of each component using item - e.g. {{item.id}} or {{item.response_data}} - and while this gives the right value (see screenshots below for component called text2), the component just will not show up; the listView stays stuck displaying "Add components".

Screenshot 2024-08-21 130343

I have no idea what's going on. Is this just a bug? As I say, it's affecting multiple listViews across different apps in exactly the same way.

A further issue, which I suppose could be related, is that I'm not able to access {{ table1.selectedRow }} today, even though I've been doing this on tables throughout my apps up until now. It again just randomly stopped working today.

Any ideas? Thank you!

Yesterday the List View was working properly but today when I open my app it is blank (like if I just added it).

Checking the component tree and my components are there yet.
is the List View broken by some update or am I missing something?

Hi @Vitor_Alano Welcome to the community! Our on call team is currently working on shipping a fix. For the time being, please see above for the temporary solution of disabling widgetgrid

This should be fixed now (thanks to our on call engineers :tada:) Please let me know if you're still experiencing this issue

3 Likes