Hello all, I have some strange happenings in one of my apps that utilizes both the Data Viewer List and Listviewer. Until recently both have functioned properly, but now when the screen loads only the first 10 items show. Refreshing using the swipe down method will load a large blank area where the rest of the items should be. So far the only way I can find to show the missing items is to click on the last item (On click: I have a custom pop up that shows more item details). I have yet to be able to reproduce this in another app as it seems to work fine in the attempted reproductions. This issue just seemed to popup up on this particular app, which is troubling since it is one of my most prized productions and would take several days if not weeks to rebuild from scratch. :grimacing: Also, I haven’t made any real alterations to the blocks in any time relative to this issue. My question is in short: Has anyone else observed this behavior recently? Any suggestions, pointers, ideas are welcome and appreciated! Thanks!

I’ve read through your issue (I added a link to your post right above this) and commented with my experience. The DVL tasks are much faster on my device. So it’s either an iPhone 8 issue or an issue with the blocks you’re using. Can you post a screenshot of your blocks?

Hi all, the problem is about the repeat cycle, all repeating cycles in Thunkable does not wait that the blocks inside the cycle finish before to start another cycle. So, if you interrogate DB like Firebase or do others blocks task, you have to put a wait block, but not inside the interrogation DB or others task block but after those, to the last block before the end of repeating block, in order to stoping the repeating and give to the previous blocks the time to finish their job. Thanks Bye

[image] info5958: if you interrogate DB like Firebase or do others blocks task, you have to put a wait block This is NOT entirely correct. When you use the Realtime DB blocks to retrieve data from Firebase then you will need to make sure whatever you are doing inside the blocks is completed because these blocks are asynchronous. However, you can choose to get the data from Firebase using Cloud Variables which are synchronous by nature and will wait until the block completes its task before giving control to the next block in your code. You have the choice but I see a lot using the asynchronous blocks for the wrong choices of actions.

It sound good :slight_smile: can you post an example about Cloud Variables used in Thunkable in that way ? Because i can not find variables named Cloud or similar but then i think my mistake. Thanks Kind regards

Check this example by @jane [image] Chat app In Thunkable drag and drop Questions about Thunkable Hi there, This realtime DB block is the same as this cloud variable block: [image] [Screen Shot 2021-05-24 at 8.00.32 AM] And this realtimeDB block is the same as this cloud variable block: [image] [Screen Shot 2021-05-24 at 8.01.27 AM] I am using dynamically named variables here, so you don’t even need an initialize block! Does that help you understand how to use cloud variables instead of the Realtime DB component in your Drag and Drop project? You can also see the tutorial video signup using cloud variables [image] Manage Signed In Users' Data with Cloud Variables Tutorials and DIY Guides Hi there, Thunkers wave I have previously shared a Sign In Video Tutorial for Drag and Drop UI which used stored variables to save the sign in details between app sessions. We now also have a video tutorial to save user details such as name and profile picture to the cloud using cloud variables! Check it out here: [Cloud Variables - Save User Data to the Cloud in Thunkable Drag and Drop UI] This includes the chapters: 0:00 Cloud variables vs Stored Variables and App Variables …

I provided an example here, too: [image] Saving partial data below a Firebase key? Questions about Thunkable Thunkable X is the current and only version of Thunkable available right now. I think what you are asking is if this can be done in the older “Snap to Place” (StP) interface instead of the newer “Drag and Drop” (DnD) interface. In both interfaces, you can find it near the bottom of the variables drawer. The set app variable "name" to [ ] block can be configured so that it says “cloud” instead of “app”. And then you enter the path to the Firebase node in the “name” section, as I showed above. […

Hi @tatiang thank you for the reply. I try to make a short description of my app: I use a data source, which is connected to airtable (I made an example app to show some restaurants in San Francisco, that’s why it is named “SFRest” :grin:): [image] use a data viewer list and connect it to the data source. That’s all. go to the “Blocks” section. The data source is listed within the blocks and understands the ID which gets returned after clicking an item in the data viewer list. I measure the time for execution (interesting: the “seconds since 1970” are precise up to milliseconds, they are not integers!). Here is an example block: [image] When you test this block you can see that after clicking an entry from the data viewer list the first time it takes some noticeable time. Now you can click on other items, but when you click on an entry the second time or so, the results come without delay! For me it is a bug (or an unneccessary delay) in the first click. This shows that Thunkable app can be very fast but in some places a “handbreak” is active. This delay also happens in “swipe left” or “swipe right” blocks, because there is also an ID, and fetching the information for this ID is also delayed the first time.

And I’m not seeing that delay. So again, it could be your device although I would think an iPhone 8 would be fast enough. You’re getting four values from Airtable every time you click a DVL item. That’s going to take a little time. What happens if you replace those four blocks with set LabelName's Text to make text from list [list of values in SFRest-->Places]? Because that’s a single call to Airtable that gets all of the values you need. I understand why you have it set up the way you do but I think you should test this with the list of values block (and for now, remove the other Airtable get value calls) and see if it’s noticeably faster.

Hi! Yes, I can definitely speed things up by using the block “get row object”, that way I only have one delay accessing the data source and can get the information from the object. All I wanted to show is the delay when accessing an item for the first time. For a single entry this delay might be ok, but… not everybody has the last and fastest iPhone / Android phone when you have 20 restaurants in your data source and want to show all of them on a map, then you get the delay multiplied by 20. And there are cases with >>20 datasets.

I understand about different devices. And I’m not suggesting you should only develop apps for the newest phones. Rather, that’s one variable… device type. Another variable is how many calls you’re making to Airtable. And maps are a whole other issue in the sense that you’d need to show your blocks for those, too. Hopefully someone else with an older device can confirm what you’re seeing because I don’t see a difference between 20 and 50 rows.

Data Viewer List - Incomplete list shown

Questions about Thunkable X

tatiang November 1, 2021, 5:30pm 31

I provided an example here, too:

Topic		Replies	Views
Data Viewer List glitches when visibility is changed Questions about Thunkable X bug	10	763	January 3, 2024
Data viewer glitched? Questions about Thunkable X	24	843	February 1, 2021
Data viewer list causes app to slow down Questions about Thunkable X	11	654	May 26, 2022
After changing the List Viewer component I have a strange problem! Questions about Thunkable X	3	426	March 5, 2021
Data Viewer List + Firebase + Local Data Source Questions about Thunkable X firebase , data-source , data-viewer	60	2321	October 10, 2021

Data Viewer List - Incomplete list shown

Related topics