I have logic on my home screen that either takes users to 1 screen or another depending on if they are logged in. But about 10% of the time, it takes me to a completely blank white screen, which none of my screens in the app are white.
@dreadnaught73849 This is usually a timing / auth state issue on Bubble Mobile. About 10% of the time the app evaluates navigation before the user’s login state is fully resolved, so it navigates to “nowhere” and shows a white screen.
Fixes:
-
Don’t navigate immediately on load — wait until login state is confirmed
-
Make sure conditions are mutually exclusive (no moment where user is neither logged in nor logged out)
-
Add a fallback route (e.g. go to login)
-
Happens more on real devices due to latency
Adding a small guard (custom state like auth_ready = yes) usually fixes it.
Thanks for the suggestion. What is the action to check auth status? Is it not ‘is logged in’?
Try with either of option:
-
When Page is loaded
→ Only when Current User is logged in
→ Navigate to Screen AWhen Page is loaded
→ Only when Current User is NOT logged in
→ Navigate to Screen B -
When Page is loaded
→ Add action: Pause before next action (0.3–0.5 seconds)
→ Then navigate based on Current User is logged in
Let me know ![]()
I tried this and still has an issue. Cc @nick.carroll see the latest report from a user:
I am actually getting this on my web app as well. I thought it was just me. Might want to do a bug report. Even a page refresh doesn’t help. I have to go back to the main page for it to work again. It’s hard to replicate, so not sure if anything will improve. Mine happens if I have the page open for a while. Then I come back to it and it is just white. ![]()
Can you share the full workflow screen and screenshots of the screen it should land on? Are you sure you don’t have conditionals in particular on the page or on the elements? Are they all visible?
Have you tried debugging in the web preview? What comes out? I also have these pages with access and I have no problem. (app on both store from feb 25)
I suggest you create two different workflows, one for when the user is logged in, one for when it is not and you have to enter the condition exactly in page is loaded. I’m sure it will work this way.
