# Screen Visibility Condition Issues

**URL:** <https://community.glideapps.com/t/screen-visibility-condition-issues/55588>\
**Category:** Ask for Help\
**Created:** [December 9, 2022, 8:29am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588 "2022-12-09T08:29:11Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![nocodenewbie](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodenewbie/32/48203_2.png) [@nocodenewbie](https://community.glideapps.com/u/nocodenewbie)\
**Post date:** [December 9, 2022, 8:29am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/1 "2022-12-09T08:29:11Z")

</div>

I have an onboarding screen that I use to onboard new users, the visibility condition on this screen is set as seen below:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/5/65f7796d5a3c3d687e4519c8b74046213a891907.jpeg)

This works as intended, however, every time someone launches the app, and the visibility condition is not satisfied (i.e. the screen should be hidden) it still popups up for a brief second before disappearing. See below, I am wondering if this is to be expected or is there something that I am doing wrong.

Screen capture: [Loom | Free Screen & Video Recording Software | Loom](https://www.loom.com/share/3afe89d04a9b466c96c3f1657af78577)

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [December 9, 2022, 8:47am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/2 "2022-12-09T08:47:46Z")

</div>

mmm, that’s not normal.

What type of column is “Onboarding Completed”?  
Is it a computed or non-computed column?  
If it’s a computed column, that could possibly explain the delay - that is, it takes a moment for the computations to happen on the user device.

---

<div class="post-metadata">

**Author:** ![nocodenewbie](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodenewbie/32/48203_2.png) [@nocodenewbie](https://community.glideapps.com/u/nocodenewbie)\
**Post date:** [December 9, 2022, 8:48am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/3 "2022-12-09T08:48:58Z")

</div>

It is a Date & Time column, it stores the timestamp when the user completed the onboarding flow. The visibility condition just checks if the “Onboarding Completed” is empty or not, so there is no computation really.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [December 9, 2022, 8:52am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/4 "2022-12-09T08:52:55Z")

</div>

Okay, that’s interesting.

Try switching the order of the tabs around. Make your Home Screen the first tab, and your Onboarding Screen the second tab.

See if that makes a difference.

---

<div class="post-metadata">

**Author:** ![nocodenewbie](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodenewbie/32/48203_2.png) [@nocodenewbie](https://community.glideapps.com/u/nocodenewbie)\
**Post date:** [December 9, 2022, 8:58am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/5 "2022-12-09T08:58:54Z")

</div>

But wouldn’t that defeat or break the onboarding flow? I want new users to see that screen/tab first.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [December 9, 2022, 9:03am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/6 "2022-12-09T09:03:57Z")

</div>

It shouldn’t, as long as you have the reverse visibility condition on all other tabs.

---

<div class="post-metadata">

**Author:** ![nocodenewbie](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodenewbie/32/48203_2.png) [@nocodenewbie](https://community.glideapps.com/u/nocodenewbie)\
**Post date:** [December 9, 2022, 9:14am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/7 "2022-12-09T09:14:38Z")

</div>

Changed the order, didn’t help.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [December 9, 2022, 9:24am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/8 "2022-12-09T09:24:06Z")

</div>

hmm, okay. I’m running out of ideas.

What are the privacy settings on your App?  
Do you require sign in, or is it optional?

---

<div class="post-metadata">

**Author:** ![nocodenewbie](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodenewbie/32/48203_2.png) [@nocodenewbie](https://community.glideapps.com/u/nocodenewbie)\
**Post date:** [December 9, 2022, 9:44am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/9 "2022-12-09T09:44:07Z")

</div>

Sign in is required.

---

<div class="post-metadata">

**Author:** ![Thoughts](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thoughts/32/46790_2.png) [@Thoughts](https://community.glideapps.com/u/Thoughts)\
**Post date:** [December 9, 2022, 9:57am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/10 "2022-12-09T09:57:39Z")

</div>

Maybe change the condition.  
Right now you set to show the tab when a field is empty. try to do the opposite.  
Create an “onboarding INcomplete” field and show tab when this field is NOT empty.

My thinking is that it takes time to load the value in the “Onboarding Completed” field, and for that loading time the field is indeed EMPTY.

Shouldn’t happen but worth a try maybe…

---

<div class="post-metadata">

**Author:** ![nocodenewbie](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodenewbie/32/48203_2.png) [@nocodenewbie](https://community.glideapps.com/u/nocodenewbie)\
**Post date:** [December 9, 2022, 10:13am UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/11 "2022-12-09T10:13:08Z")

</div>

Tried doing this and it is still the same.

---

<div class="post-metadata">

**Author:** ![nocodenewbie](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodenewbie/32/48203_2.png) [@nocodenewbie](https://community.glideapps.com/u/nocodenewbie)\
**Post date:** [December 9, 2022, 3:08pm UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/12 "2022-12-09T15:08:11Z")

</div>

I even tried using a boolean column but the problem persists. Have sent a support request to Glide let’s see if someone replies.

---

<div class="post-metadata">

**Author:** ![George-Glide](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/george-glide/32/22384_2.png) [@George-Glide](https://community.glideapps.com/u/George-Glide)\
**Post date:** [December 13, 2022, 1:38pm UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/13 "2022-12-13T13:38:02Z")

</div>

FYI, for future readers of this thread.  
The issue was that the field used in the visibility condition was set up as user specific. The reason that the screen briefly showed was because of a slight delay in getting the data for the logged in user.

Only in rare circumstances would you ever have a user specific column in the Profile/Users file as you would normally only allow the logged in user to write to their own row in that file.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [December 13, 2022, 1:55pm UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/14 "2022-12-13T13:55:42Z")

</div>

> [@George-Glide](#):
>
> The issue was that the field used in the visibility condition was set up as user specific. The reason that the screen briefly showed was because of a slight delay in getting the data for the logged in user.

ugh!  
This is a great example of where if a screen shot of the table was provided, we probably could have spotted that immediately, and saved a support request.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [December 14, 2022, 1:56pm UTC](https://community.glideapps.com/t/screen-visibility-condition-issues/55588/15 "2022-12-14T13:56:40Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
