So the problem that you are having is that the screen is empty??? I wasn’t sure, because your screenshots and video only show what appears to be the app working correctly. It just needs to be clear what is not working when you say “it’s not working”. I didn’t realize that is was a problem with an empty screen. Based on what you showed, I thought maybe you had an issue with the submit button, but the submit button must be working correctly?
Do you have visibility conditions on the components on the screen? Can you show what those conditions are? I think I have an idea. I think you are checking for ‘false’ for some of your components. You should never ever check for ‘false’. You should only check for ‘true’ or ‘not true’. A boolean column can be in one of three states. ‘blank’, ‘false’, or ‘true’. If you are checking for ‘false’ instead of ‘not true’, then you are ignoring the possible condition of ‘blank’, which will always be the case since your app is public. User Specific columns on a public app will always reset to blank when you close the app. When you sign in, it’s probably using the last saved value for the boolean, which may be ‘false’ instead of ‘blank’, so it happens to work for you when you are signed in. I would be willing to bet that if a brand new user signed into the app, it also would not work, because the default value of that switch boolean column is blank. I would have tried to sign into your app, but it doesn’t appear to be showing the hamburger menu, so I can’t sign it to test that theory. I think your problem is that have visibility conditions that check for ‘false’, but instead should check for “is not ‘true’”.
Your other forms work correctly because you are using the native glide form, which does not use user specific columns, and doesn’t appear to have the same visibility conditions (based on the switch) that you have in your custom form.