Yes that way can work but I donāt know if is the best way, I will try and test to seeā¦ thanks for help
If youāre trying to limit the visibility to only signed-in users that would work, because when theyāre signed in, their user email wonāt be empty.
well I have to test because need another button, one for Non singned user and one for signed userā¦ it will be great if the components or the inline list have a feature to send automatically to sign in screen if user are not signed.
Yeah, Iāve never understood this warning even though it doesnāt affect me personally. Especially with the āuser profileā workaround and the āset to public with email, make the change, then set to public againā workaround. I have yet see or hear of these workarounds not working. Makes sense that the warning should go awayā¦ especially with the new button action.
In a details view, make 2 inline lists. One with visibility user email is empty and set action to sign in, one with visibility user email is not empty and set action to view details. That way I think it would work.
This is it! now 1000000% GDPR compliant!
As an Asian I laughed way too hard at Han Some.
Omg, thanks for that Team! I was really anxious for this
Hi Roberto, I had the same problem because I have a lot of components with visibility for āsigned-in userā
I changed it to āemail is user emailā and it worked perfect for me.
Amazing feature!
Any solution for this limitation for public app?
1- Filter by user signed email
2- Edit by user signed email
@Brice - weird question. But even when you have the āwarningsā does the filter STILL WORK?
In my app, I am getting the warningā¦
But in the APP it still works!
ME Signed in:
Other teacher NOT signed in.
So even though the filter says it does not work, it does. (for me)
(my app link: https://myclassapp.glideapp.io/
Despite the warning, It does work I have tried it on several apps
Weāll fix that warning soon.
Once signed in, is the login preserved if you close the app? Previously, my experience was that public apps that used this work-around (force visibility settings by switching from public to email sign-in then back again) would lose the login session when the app is closed.
Good one. But I have a question.
Does this mean the launch page can have only one button that triggers Sign in?
The way my launch page (currently the one that comes after Sign in) is designed - it has some buttons leading to content which are open to public in ideal world) but it also has some buttons where Sign in is a must (like my account / email verification is needed).
How should I go about using this feature in my case? Thanks for any help.
Thank you! Thank you! Thank you! This is EXACTLY what Iāve been trying to figure out how to do. I am not sure how to apply it to the app that I have already published - hopefully a video will be coming shortly.
I think your pleased
Thank you @JackVaughan!
If we want to Preview As our public app as a non signed-in user, then see post sign-in, how do we do? (in my picture, ātoto@emailā appears to be signed-in anytime)
Thanks
@AyS_0908 are you using user profiles? What happens if you type in an email thatās not in the user profile sheet? I imagine if you set conditions based on values on the user profile sheet, you would see what a non-signed in user sees. Refer to @Robert_Petittoās videos to see what I mean.