Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUGS - related to login #238

Open
1 task done
alx-xlx opened this issue Jul 9, 2024 · 3 comments
Open
1 task done

BUGS - related to login #238

alx-xlx opened this issue Jul 9, 2024 · 3 comments
Labels
Status: Created The issue has been created but not yet assigned or addressed. Type: Bug Something isn't working

Comments

@alx-xlx
Copy link

alx-xlx commented Jul 9, 2024

Avoid duplicated bug reports

  • I've found a bug and checked that there are no open or closed bug report related to this.

Description

Whenever I refresh the browser I have to again enter the server url and login. It shouldn't do that

Please strip the whitespaces from username and password inputs

Local environment

No response

@alx-xlx alx-xlx added Status: Created The issue has been created but not yet assigned or addressed. Type: Bug Something isn't working labels Jul 9, 2024
@MDeLuise
Copy link
Owner

MDeLuise commented Aug 1, 2024

Hi @alx-xlx, thanks for reporting this.
I was not able to reproduce the issue where the app asks for the server URL and login again after refreshing the browser. I’ve tested it on firefox and attached a screen recording demonstrating that the app retains the login information upon refresh.
Could you please provide more details, such as the browser version, or specific steps to reproduce the issue?

Screen.Recording.2024-08-01.at.15.54.14.mov

@John710
Copy link
Contributor

John710 commented Aug 5, 2024

I get the same error. In Google chrome browser version 127.0.6533.89, And also in another browser on the chromium engine.
It does not occur with every update, I could not understand the reasons.

@MDeLuise
Copy link
Owner

Hi there! I'm currently reviewing some older issues, and I wanted to check if this issue is still affecting you. With the latest release of the project (0.9.0), which includes numerous dependency updates and bug fixes, there's a chance the problem might have been resolved.

Could you please confirm whether you're still experiencing this issue on the latest version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Created The issue has been created but not yet assigned or addressed. Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants