Glide is saying Account Does not Exist!

Glide is saying my account does not exist. I was literally just in there working on it when it glitched out and logged me out. Now when I go back in, it says the account is not there.

Is this happening to anyone else? Help?

Are you sure you logged in with the same email/gmail?

Yes, absolutely sure. It is my bosses account, and I have proof that she just upgraded to the pro account. I did see that 20 days ago there was a glitch and the engineers needed to fix it so hoping this is the same thing again. I was literally just in there working on it.

Probably create a support ticket

1 Like

Have you tried logging in from a different browser? In incognito mode?

Yes, and yes. There has to be something that can be done. All I did was go in and add a row owner. When I went to refresh, it kicked me out and now it says I have no account at all. I can show the receipt from a few weeks ago.

Contact the Glide support desk

This is still unresolved. Getting really frustrated. I need to be able to use this app!

Unresolved because customer support hasn’t gotten back to you? Or unresolved despite them getting back to you?

@SantiagoPerez @George-Glide @DarrenHumphries

Unresolved by support who I have been in contact with. On one hand I know they are trying but on the other hand it is very much lacking considering I have not had the app for a week. At first I could not log in, which I can now. I told them my app was completely missing from my dashboard. They sent me a Loom instruction video to test something in developer tools. This doesn’t help me considering my app is completely gone. I should not have to wait days to get inconsistent and shoddy help.

2 ideas:

  1. I have no idea how Glide’s customer support handles tickets, but if it is an option to them (probably based on the load of requests and time zones and whatnot), you could ask for synchronous help via a call or chat, rather than asynchronous. Asynchronous communication can drag on.

  2. Of no consolation here, but perhaps a way to turn this experience into a positive would be to try to draw a learning so it doesn’t happen again. I probably don’t do it enough, we probably all should do it whenever possible: since project change history is not available, if you have room in your plan, it could be a good practice to create regular backups of your projects.


Only a developer would expect .GIT level history. No-coders don’t expect it, and don’t expect server crashes, either.

I make duplicates of my apps after every major revision.

One thing I’ve seen others mention that I would also like to see is the ability to bring my app backup local (a single encrypted file that is nothing but a backup with a unique name assigned by the user that could contain a version number).

The backup would be unable to be used except to be re-loaded to the Glide server in the event of a catastrophic failure of the user account. I have seen a few cases of that reported just in my six months using Glide, and in the last two weeks, I’ve seen a couple reporting lost work. Sure, two were people that accidentally deleted their app, but a few were users whose accounts or apps malfunctioned to the point of losing work and/or data.

For myself, I am glad I have been keeping incremental copies of my apps. Just a few weeks ago, one of my users reported that a feature that used to work no longer worked. Since I had not done any work on the app in almost two months, I was skeptical. But sure enough, the custom action was missing entire parts of logic. It wasn’t that the action was missing, but parts of it were. I actually had to go back several revisions to find a copy of my app where the logic was intact, and I re-created it in the current app. My point is that things malfunction. Barring Glide actually making regular copies of our app for us; I think if we are willing to make space available on our local systems to host backups, they could accommodate that easily.

1 Like

Thank you both @David_Gabler and @nathanaelb you two have been more helpful and insightful than Glide support. I have learned my lesson and will backup any app I make. I had intended to do so, but failed to do it in time. I did not realize all my work was in such peril. My question now is do I even rebuild with Glide? I feel like their support has been okay, but mostly nonsensical. Would you rebuild? Perhaps I should hire an expert, but I would be losing money. I wanted to become really good at building Glide no-code apps but now I am not sure.

1 Like

For context, Glide launched in mid to late 2019 (I believe) and grew a lot in 2020 and 2021. The company is recent but the team has a strong track record. The feature releases in the past two years have been mind blowing. But not all is rose: the platform can a little buggy at times and building has become slightly less user-friendly than it might have been. The trade-off has been more power, more features. It is a difficult balance to strike. According to the CEO of Glide, 2022 will be spent reinforcing Glide’s foundations: simplicity, user-friendliness, fun.

Note that Glide recently closed a round of funding, so the team should be expanding and giving themselves the means to fix bugs, simplify, etc.

In the best of worlds, the bugs in the product would be so rare, and the product so easy to use, that support would barely be needed. The community forum is here, however, so we can help one another collectively.

It’s a valid question. There are many other solutions out there and they all have their pros and cons. Glide is by no means perfect but it aims to cater to a certain market (type of user) for certain use cases. Do you fit the ideal Glide user and are you aiming to build what Glide can tackle? Might other platforms be more suitable? You can ask in the forum if you are unsure.

The whole point of Glide is to allow non-experts to build their web and mobile apps. In fact, in my view, it’s still one of the weaknesses of Glide: too many great things are being built by developers that have great Glide skills.

(Maybe this is not surprising: most Word documents, Powerpoint presentations or Excel sheets, for instance, are not great.)

I feel like a Glide developer might follow the following learning curve:

  • Beginners can built good looking, basic apps with little to no learning curve (+++).
  • As soon as the app is beyond basic, building features can become difficult. At the very least muddy and messy. The tinkering starts. Is this the case with other platforms? I don’t know, I only use Glide (+/-)
  • Finally, advanced users can build incredible features by pushing the limits of the platform. And here lies both a strength and a weakness: sure such and such feature is doable, but it often is not that simple (yet), involves workarounds right and left, and a lot of effort. (+ for advanced users)

As mentioned above, Glide is working hard to simplify things, and the team has proven time and time again that it delivers and never disappoints.

A response I wrote a while back: Glide vs. competition

1 Like

Hi Violet,

It isn’t, really. Hundreds of people produce thousands of apps with Glide with no mishaps.

But through experience (30 years+ of working with computers), I know that the impossible happens every day. One wrong mouse click (clicking the yes button when you mean to click the cancel button) can delete your app.

I once worked with a support person who went in the core app directory (in the DOS days) and typed “del .”. All the programs, but more importantly, all the data was wiped out in the blink of an eye. Their only backup was months old.

I never take anything for granted anymore. Ever. I have rotating backups of my stuff so I don’t risk overwriting my only good backup. I store backups off-site.

That’s why, even with many duplications of my apps in Glide (one for every version or major change), I still would like to see Glide provide us with the means to securely store our apps and Glide Tables intact off-site. It could be one big encrypted file (we don’t need to see what’s in it), with just the option to upload it to the Glide server if need be.

This being your first experience with Glide is unfortunate. I have developed in AppGyver (a very powerful no-code tool like Glide) and of all the other options that exist, I think it’s the only other tool besides Glide that I would use if Glide did not exist. My reason for sticking with Glide: it is it is certainly easier to develop good-looking user-intuitive apps, and with the multitude of videos available by @JackVaughan and @Robert_Petitto and @Darren_Alderman it is very easy to learn.

AppGyver uses Firebase as the back-end database (which I believe is the same as Glide Tables), but you have to build the Firebase databases yourself and deal with all the security issues yourself and tie them to your app yourself. As far as screen design, it’s certainly not as intuitive as Glide. In other words, the power of AppGyver comes with the trade-off of needing more advanced knowledge.

It took me a few hours without using a template to build my first Glide app – when starting from an already-designed database in Google Sheets. It took me a week to get my first one-page app with AppGyver going – just because of the back-and-forth on the user forum – no where near as active as Glide’s forum.

Glide’s community cannot be beat.


The app in question is not lost, deleted, or in peril–it was in a different account as we first suspected. There was a mixup with sign-in methods (sign-in with email versus sign-in with Google) preventing @Violet_Goode from accessing her account.

Closing this thread now.