🐛 Bug Report: v1.2.0 language switching glitch on first use #187

Closed
opened 2025-10-09 16:31:21 +03:00 by OVERLORD · 9 comments
Owner

Originally created by @bfqrst on GitHub.

Reproduction steps

  1. update to v1.2.0
  2. my language defaults to german
  3. go to my profile and manually switch to english (or any other language for that matter)
  4. animation kicks in, language stays german
  5. logout -> logout screen is german
  6. log back in and language is now reflected to be the new language (english in my case) set in step 3
  7. change the language setting again -> this time the setting is reflected instantly

Expected behavior

I think the intended behavior is that the language setting should be instantly reflected when set from the dropdown.

Actual Behavior

Animation kicks in and the language is not actually switched in the UI, but remembered in the backend.

Version and Environment

v1.2.0

Log Output

No response

Originally created by @bfqrst on GitHub. ### Reproduction steps 1. update to v1.2.0 2. my language defaults to german 3. go to my profile and manually switch to english (or any other language for that matter) 4. animation kicks in, language stays german 5. logout -> logout screen is german 6. log back in and language is now reflected to be the new language (english in my case) set in step 3 7. change the language setting again -> this time the setting is reflected instantly ### Expected behavior I think the intended behavior is that the language setting should be instantly reflected when set from the dropdown. ### Actual Behavior Animation kicks in and the language is not actually switched in the UI, but remembered in the backend. ### Version and Environment v1.2.0 ### Log Output _No response_
OVERLORD added the bug label 2025-10-09 16:31:21 +03:00
Author
Owner

@stonith404 commented on GitHub:

Thanks for reporting this issue. Yeah this is caused by 2440379cd1, which fixes an issue the automatic language detection. As language is now stored in another format this issue may occur.

Were you logged in before you upgraded to v1.2.0?

@stonith404 commented on GitHub: Thanks for reporting this issue. Yeah this is caused by 2440379cd11b4a6da7c52b122ba8f49d7c72ce1d, which fixes an issue the automatic language detection. As language is now stored in another format this issue may occur. Were you logged in before you upgraded to v1.2.0?
Author
Owner

@bfqrst commented on GitHub:

Understood. I'm pretty confident I wasn't logged in. If I'm not mistaken in v1.2.0 this occurs every time you re-deploy.

@bfqrst commented on GitHub: Understood. I'm pretty confident I wasn't logged in. If I'm not mistaken in v1.2.0 this occurs every time you re-deploy.
Author
Owner

@stonith404 commented on GitHub:

But this only happens when you restart Pocket ID? Or does it happen every time in Brave, even in a private browser window?

@stonith404 commented on GitHub: But this only happens when you restart Pocket ID? Or does it happen every time in Brave, even in a private browser window?
Author
Owner

@stonith404 commented on GitHub:

So if you restart the container the issue occurs again?

@stonith404 commented on GitHub: So if you restart the container the issue occurs again?
Author
Owner

@bfqrst commented on GitHub:

Sorry, I lost track of this... It appears as if this might be Brave related. In Brave if you switch the language the animation kicks in but nothing happens. In Firefox on the other hand, the chosen language is instantly reflected.

@bfqrst commented on GitHub: Sorry, I lost track of this... It appears as if this might be Brave related. In Brave if you switch the language the animation kicks in but nothing happens. In Firefox on the other hand, the chosen language is instantly reflected.
Author
Owner

@bfqrst commented on GitHub:

Currently I'm testing the latest new. So Brave private tabs work as expected. Language changes are reflected right away and stay that way. From what I can tell even if you restart the container. Brave regular tabs on the other hand don't reflect any changes. Does that make sense?

Let me know if you need more info!

@bfqrst commented on GitHub: Currently I'm testing the latest _new_. So Brave private tabs work as expected. Language changes are reflected right away and stay that way. From what I can tell even if you restart the container. Brave regular tabs on the other hand don't reflect any changes. Does that make sense? Let me know if you need more info!
Author
Owner

@stonith404 commented on GitHub:

Thank you. Would you mind to share the value of the locale cookie from your browser dev tools? After that please try to remove the cookie and let me know if the issue is gone. I suspect that the browser still stores the old locale format which could break the newer versions of Pocket ID.

@stonith404 commented on GitHub: Thank you. Would you mind to share the value of the `locale` cookie from your browser dev tools? After that please try to remove the cookie and let me know if the issue is gone. I suspect that the browser still stores the old locale format which could break the newer versions of Pocket ID.
Author
Owner

@stonith404 commented on GitHub:

Thanks. Yes, it's not ideal that the cookies have to be cleaned manually. Since no one else has reported this issue, I'm closing it. If anyone else has this problem, please feel free to comment, and I'll look for a better solution.

@stonith404 commented on GitHub: Thanks. Yes, it's not ideal that the cookies have to be cleaned manually. Since no one else has reported this issue, I'm closing it. If anyone else has this problem, please feel free to comment, and I'll look for a better solution.
Author
Owner

@bfqrst commented on GitHub:

Awesome, that was spot on. There was indeed a second session cookie, that took precedence over the cookie with an expiration date. The latter did indeed change with every language switch, but was overruled by the former!

Deleted the session cookie, everything works as expected. Thanks @stonith404

@bfqrst commented on GitHub: Awesome, that was spot on. There was indeed a second session cookie, that took precedence over the cookie with an expiration date. The latter did indeed change with every language switch, but was overruled by the former! Deleted the session cookie, everything works as expected. Thanks @stonith404
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id-pocket-id-2#187