Login window for Basic Authentication disappears after returning from the password manager
Hello everybody, Since the last major update (the address bar can be seen at the bottom of the display since the update), the login to a website via Basic Authentication no longer works if I use the Keepass2Android password manager to enter the password. If I want to log into a website using Basic Authentication with Firefox, the dialog box for entering a username and password appears first. In the Username field, instead of entering the name, I choose the function "Fill in with Keepass2Android". It then switches to the Keepass2Android app and I select an entry there. After the selection, it will switch back to Firefox for Android. The input field for username and password is filled and can only be seen for a fraction of a second before it disappears. However, it is not possible to register without pressing the "OK" button and I cannot access the website. I've already tried every possible setting in both Firefox and Keepass2Android. Unfortunately without success. A new version of Keepass2Android has not been released in the meantime, so that the cause is very likely to be due to the new Firefox version. I'm using a Samsung A50 with Android 10. Thank you in advance for your support. I am at your disposal for questions. regards Michael
All Replies (5)
Hello everybody, I have a little addendum on the subject: The problem is known to even more users. There is also an error message on Keepass2Android: https://github.com/PhilippC/keepass2android/issues/1399 regards Michael
Thank you for that link and your question.
Looking at this link, it appears that this issue is fixed in the Nightly variety of Firefox for Android and should therefore be in the Release version once it has passed the Beta stage.
unfortunately that is not the case. The comment at https://github.com/PhilippC/keepass2android/issues/1399, which indicates that the problem could be solved, is from September 18, 2020. The last version of Firefox that had this problem, however, is from October 16, 2020. This was released four weeks after the comment and has brought no improvement. In addition, the comments after September 18, 2020 show that the problem was apparently not yet resolved in the nightly of September 18, 2020.
Nevertheless, I will install the current beta from the Play Store and report the result of the test here.
At this moment I tested version 82.0.0-beta6. There is no change in relation to the behavior mentioned. Unfortunately the problem persists. I will probably have to switch to Chrome, at least temporarily, with a heavy heart :-(
I am sorry to hear that. The fix that you saw would have landed in Nightly first, before moving to Beta and later Release.