Users unable to log out after changing the app domain

Need help
1

We moved a bubble app from main domain to a subdomain.

After the move, users can login to a new session, or navigate to their dashboard, but when trying to logout, the following error pops up “Sorry, your login session has changed / expired… please try again”, and they are never able to log out.

Is there a way to fix this on our end, and without having to ask users to delete their browser cookies?

Thanks!

2

Not sure why this is happening. Two things I would do is:

  1. Make sure that the user is not able to access their dashboard if they are logged out. Ensure that related conditions and workflows are set in place. If bubble says that the ‘login session is changed/ expired’, then the user should not be able to access it either.
  2. Try the action ‘Log out all user’s sessions’. This can also be a scheduled workflow and you can just run it for all users so they can login on the new domain again.

Reach out to Bubble support if the issue still persists.

Hope this helps!

3

Thanks for the reply.
The user CAN indeed access their dashboard, because the app (Bubble) thinks the user is logged in. However, the user is not able to log out of the current session, whether it’s directly using a logout action, or via another browser session using the “log out all user’s sessions” action. It’s a limbo state where the user cannot log out to log back in, and cannot do much in the app while Bubble/app believes they are still logged in.

4

Do you have a workflow set up like this? If not, you might want to add it.
On page load → Go to page ‘index’, Only When the Current User is not logged in.
Or
Current User is Logged Out → Go to page ‘index’

5

Yes, I do.
The problem is that the app thinks the user is logged in based on the cookies from the old domain, but is not able to log the user out. It’s a very weird limbo state.

6

We’re experiencing the same thing having just moved the app from domain to subdomain. Looks to be two different sets of cookies trying to do the same work. Have you had any luck with a solution?

7

The Bubble engineering team are aware of that issue, but they said it wasn’t a priority for them to fix at the moment, and that we should ask our users to clear their cookies, instead.

8

Thanks for your quick response. Pretty frustrating for sure. We’re continuing to look for a solution and will keep you updated if we find anything, but I’m guessing you’ve accepted your fate by now. Out of curiosity, did you have any user drop-off because of the issue or do you have any suggestions on how to handle it with users?

9

We had to revert the change from the subdomain to the main domain due to the extremely confusing situation and the fact that it took the support team over a week to respond.