Multiple Bugs While Building My App in Glide

Team ID: dfVQyCwAX7aK1jBRmJzi

App ID: 2ENyoormnImSjDEoQSYi

Subject: Multiple Bugs in Glide Editor

Hi everyone,

While working on my app today (before release), I encountered several bugs and would love to know if others have experienced the same, or if there are known workarounds:

  1. Collections & Tabs – On a screen with two collections that should toggle by tab, sometimes the visibility works, and sometimes it doesn’t.

  2. Component List – After opening a screen via a button and going back, the left panel still shows components from the screen I just left.

  3. Buttons & Workflows – Some buttons stopped working even though workflows were set. Later they suddenly worked again without any change.

  4. Collection Actions – When setting up actions for a collection, I wasn’t always able to select that collection’s source (it offered unrelated tables).

  5. Rollup Columns – Rollups calculated correctly in the Data Editor, but showed different values in the Layout.

  6. Performance – The editor is slow and occasionally freezes when adding components or defining workflows.

Has anyone else faced these problems? Any tips or fixes would be appreciated.

Thanks!

If you can show how some of these things are set up, we might be able to help. To begin though, I would suggest clearing your browser cache and cookies to see if some of the issues clear up.

How do you have this set? I assume you are using the Tabs component and not the Tabs Container component? I assume you tab write a value to the table and your visibility conditions look at that same value?

Try clearing browser cache.

Try clearing browser cache.

Try clearing browser cache. If the doesn’t work, it may depend on how you are trying to set up the actions or the workflow. Are you trying to connect to a table, relation, or query? Does it maybe not have enough context to know which screen/table you are coming from?

This is commonly due to expecting data from rows under row ownership. You may see the expected numbers in the data editor, but the app itself doesn’t even know that unowned rows exist, so the rollup will only be able to see and use rows of data that the user owns.

Hard to say with this one. Could be due to a lot of content in your app, or inefficient structuring of your data tables. Would need to know more about your app, where it is slow, and what you are doing when you see these performance issues.

Screenshots are always helpful to help explain your issues. They provide a lot of clues.

3 Likes

Thank you so much for your detailed reply — it really helped me.
I tried clearing my browser cache and I hope this will resolve some of the bugs I’ve been experiencing.

Regarding the Rollup columns, your explanation makes perfect sense. I realized I do have Row Owners set up in my app, so that explains the behavior I saw.

As for performance, the slowness and freezing mostly happen when I’m creating or editing workflows.

Next time I’ll make sure to include screenshots as well, since I understand how much that can help.

I do have one question: what is the main difference between the Tabs component and the Tabs Container component? And why do you think the issue may be happening because I used Tabs?

Thanks again for your clear and supportive guidance. I’ll continue working with the app for a few more days, and I’ll update if I still run into these kinds of bugs.

Much appreciated!

Visually, they look the same but there are key differences in how they work.

As the name suggests, the Tabs Container provides a container where you can simply place components into each tab and only the components under each tab will be visible. Very easy setup as you don’t need to store the selected tab value in a table column and you don’t need to apply any visibility conditions to your components because they each live inside their respective tab container.

On the other hand, the Tabs component is essentially a choice component design to look like tabs. To use it effectively, you need to write the chosen tab to a column in your table and then apply visibility conditions to any components you want to hide or show based on the chosen tab.

I’m not say one or the other is good or bad. I’m just looking for clarification on which one you are using because they each work very differently. If you are using the Tabs component, then I’d like to see the setup. Then column it’s writing to, and and visibility conditions that you say are not working.

2 Likes