Help - my published app is showing up blank!

Hi everyone,

I’ve been dealing with a persistent issue in my Glide app and could use some help or insight from the community.

App URL: https://deendeals-yuz2.glide.page/
Data Source: Glide Tables

What’s happening:

  • Everything looks and works perfectly in the builder preview.

  • But the published version (both web and PWA) shows a blank screen.

  • This affects all users, across multiple devices, browsers, and networks.

What I’ve already tried:

  • Tested in incognito mode and multiple browsers (Chrome, Safari, Firefox)

  • Cleared cache, restarted devices.

  • Confirmed that visibility conditions and filters aren’t hiding content

  • Verified that data is syncing normally in Glide Tables

  • Published several times, even after small data and layout changes

This issue has been ongoing for 3–4 months, so it doesn’t seem like a simple caching or visibility issue. Since the builder preview works fine but the published app doesn’t, I’m wondering if this could be related to a service worker or published build problem.

Question:
Has anyone encountered something similar where the published version is blank for all users, but the builder preview works perfectly?
And if so, did duplicating the app or asking Glide support to reset the published build fix it?

Thanks so much in advance. Any guidance would be appreciated!

Samir
DeenDeals

Just checked the link - the app is not blank for me.

mobile iOS

Are you saying it’s blank once the user has signed in?

Hey Rose, thanks for trying and looking into it!

That’s correct - it shows up as blank once the user does the initial login and and it directs them to the home page.

There are two types of users that can be selected - Store or Customer. Based on the user type, only certain screens will be available to them. I have triple and quadruple checked my screens to ensure that the viewing filters are set for User Type IS Store (for the Store screens) or User Type IS Customer (for the Customer Screen).

Initially, the user type for some reason was being overwritten as blank (even though I checked the use cases for the User Type column to ensure that it was not being overwritten), which would make sense why the screens were blank. But now, the user type is not being overwritten, but this issue still persists.

Anyone can feel free to login and try to go the main page - after onboarding, the issue typically happens when trying to navigate to a different tab or if a user logs out.

Seems that your onboarding flow starts with one tab and then progresses to a second tab. Do you have any visibility conditions for either of your onboarding tabs? Wondering if you are still letting the first tab display due to a missing visibility conditions on the tab itself, but have only hidden the components in that tab so it appears blank.

Every time you come back into the app it goes to that first tab initially, and if you have hidden all components and are somehow hiding the tab bar, then the user is getting stuck.

1 Like

Is it possible to invite me to your team to diagnose this? As Jeff said, I want to check for visibility conditions, and if the screens are tied to the correct row in the onboarding flow.

1 Like