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!
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.
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.
You all are awesome! Just wanted to clarify a few things:
the onboarding page column for the assigned user is 6, which is correct and should show the main app screens and not the initial onboarding screen. The onboarding screen only shows if Onboarding Page IS empty.
Now, I am realizing that the nexus of this issue is probably what I feared initially - an override of the User Type column. As before, the User Type column is appearing as blank, and I have no idea why, because it is only written to once, and then should not be touched afterwards.
Mind you that this user profile setup is a container which sits in the mandatory User Profile screen.
Screenshot of User_Type being overriden (left hand most column):
I do not have linked tables with another app - I duplicated the app but I can confirm that the tables are not linked because the new users that have been added do not show up in the second duplicate app.
Blank = Animated Welcome Gif, screen 1
1 = ToS, screen 1
(Can’t remember why 2 and 3 are skipped)
4 = Are you a customer or a store?, screen 1
5 = enter your profile info, user profile screen
6 = redirect to home page
I’ve had a couple of beta testers before, and this would always happen with them - they would select to be a user, try out a couple functions of the app, only to try to login and come to the blank screen.
Each time, I’ve noticed that their user type got overridden. It is just a plain text column.
If it is, then that explains why it is always blank. You cannot change that column with a User interaction workflow. The only way to change it is via the API, or with a server side workflow.
If you’re not actually using Roles as Row Owners anywhere, then the simple fix is to remove it from your User Profiles configuration.
Did you see Darren’s response? You seem to be responding only to Thinh. I see you are responding by email, but I suggest coming back into the forum to see the entire conversation.
I had made a completely new plain text column that effectively acts as a role, but doesn’t have the Role subject or title (name of column is “User Type”).
Is it possible that Glide treats that as the Role column, thereby continually overriding it?
If it is overriding it, any suggestions for workarounds would be greatly appreciated, because I want the user to select a role (e.g. Customer/Store), and then that role should remain permanent.
You need to look at your user profile configuration as Darren showed to determine if a column is designated as a true Role column. Just naming the column “Role” does not make it a true role column.
