Every time I close my browser and then open it, Glide logs out (the builder – all Apps stay logged in).
This is recent within the last couple of weeks. I thought it was just a fluke, but it keeps happening every time.
How can I fix this?
That behaviour suggest that the authentication cookie isn’t being saved.
- Have you changed any of your browser settings recently, specifically with regards to cookies?
- Have you installed any new extensions that might possibly be getting in the way?
- Do you get the same behaviour if you open the builder in another browser?
- Do you get the same behaviour if you sign into one of your Apps using the same browser?
Answers to the above questions may provide clues.
3 Likes
I haven’t changed anything, and all my apps stay signed in (in the same browser).
I don’t like any other browsers, and since I “sign in with Google” that’s the only browser I’ve ever used. Not sure if I could sign in without it.
So to clarify, this only happens with the builder?
I would suggest trying it on another browser to see if the browser is the culprit here.
1 Like
I wasn’t suggesting that you switch to another browser, just to try another browser to see if that helps to isolate the cause. Troubleshooting 101 
2 Likes
It seems to stay signed in using Edge. So how do I make the “authentication cookie” stay put? I have made no changes in anything on my computer in five years. I keep getting warned by Microsoft that they will update me to Windows 11 without my permission if I remain this stubborn.
If you’re on Chrome, I would advise checking chrome://settings/content/siteData to see if Glide was added to the “delete” list.
2 Likes
If it isn’t the culprit, I would think that’s because of an extension. Do you have any extensions installed on Chrome? Can you try disabling them all to see if it helps?
1 Like
I’d probably go to site settings, and delete site data for glideapps.com or just delete all site data (clear cache/cookies). Could be a corrupt cookie.
3 Likes
Thanks, Jeff!
I also need to thank @Darren_Murphy and @ThinhDinh whose valuable contributions led us to the solution.
It must have been a corrupt cookie.
And on that note, let me impart some sage wisdom, “He who eats cookies in bed has a crumby night.”
4 Likes
Well, it started happening after two browser closes. So I turned off all extensions, per @ThinhDinh, but I only had a few anyway, and no new ones. Still no good.
Hard to imagine my cookies getting corrupted so easily. DIsk scan shows no errors.
Really hard to say. If the cookie is not actually corrupt, then something is unique to your situation and causing that cookie to expire on exit or in a short amount of time. I’m guessing there is a setting or something that is causing that, but I’m not sure what to look for.
2 Likes
I agree.
Try checking this part: //settings/content/Third-party cookies. If it still doesn’t work, reinstalling Chrome might solve the problem rather than searching for a needle in a haystack.
2 Likes
Thank you. They were already allowed. I did explicitly add Glide as you suggested. We will see…
1 Like
I didn’t add it explicitly; it happened automatically. There might be a setting in your browser that’s not functioning properly.
1 Like