Open chrisvdb opened 4 years ago
Same issue
The same problem with Mi 9T. I believe appeared after upgrade to Android 10.
@eliserichards Please consider revising priority, since it is not Redmi 8 specific and probably affects most of the recent Xiaomi device.
Workaround is too unlock Lockwise manually, then it is possible to select password from popup list. Unfortunately search does not work either, so if Lockwise fails to match correct domain name, user have to open Lockwise application and search there, and then manually copy password.
Looks like this is not a Lockwise bug, but happens due to aggressive MIUI optimizations. @chrisvdb @Marocco2 enabling "Display pop-up windows windows while running in the background" in "Other permissions" section solved problem for me.
@yura-pakhuchiy thanks a lot, that worked!
Not entirely sure if this is a Lockwise bug or not, but I would have expected to be requested for the permission on installation or first use. I'll leave it up to one of the devs to decide if this is a bug or not, and close this issue.
I doubt there is a way to request this permision during installation since it is a Xiaomi specific extension. But some hint to user would be nice, for example if pop-up window creation fails, Lockwise can record this and ask user to grant the permission on next manual start.
Thanks @yura-pakhuchiy! your workaround fixed my issue as well.
Hello I have the same issue for a long time now on my Xiaomi 9T Pro
Attach two videos :
First test : Video Test 1 1 - Kill all app 2 - Launch Microsoft Teams 3 - Into the form to complete "Unlock Firefox Lockwise" is displayed 4 - Clicking on it doesn't do anything
Second test : Video Test 2 1 - Kill all app 2 - Launch Lockwise and unlock it 3 - Launch Microsoft Teams 4 - Into the form to complete "Unlock Firefox Lockwise" is not displayed now and I can select the login
Is it possible to have an answer? Impossible to use correctly Lockwise on my mobile for long months now and I see this bug is a "P5" priority?
Enabling "Display pop-up windows windows while running in the background" in "Other permissions" (as described above) worked for me.
Thanks but doesn't change anything for me :(
Steps to reproduce
Expected behavior
Actual behavior
Device & build information