1PasswordAutofill works in every app that isn't Chrome (i.e. Firefox is fine). Some apps are hard coded to use Chrome for their login screens. These don't work either. Chrome only suggests from the Google Password Manager. Selecting a new autofill service (or even none) has no effect. The Chrome settings have "offer to save passwords" and "auto sign-in" turned off. Unlike the instructions, these options are underneath a cog icon on the "Password Manager" menu, not the "Passwords" menu, which doesn't exist.
If you have saved passwords, Google's Password manager will continue suggesting them even when turned off in Chrome. To stop this you can use a computer to move your saved passwords in Chrome to 1Password, then delete them from Chrome.
Thanks for the help. I've deleted all passwords from Google (labourious process without a delete all) and it made no difference (although I needed to do it anyway). Eventually, I found a special setting under the "Google->Autofill" settings that gives Chrome special override access over your actual Android configured auto-fill provider. Switching off the special "spuriously ignore autofill settings not set to Google" setting does the trick. It might be worth mentioning in the docs, although the setting is actually called "Use Auto-Fill with Google". Completely unnecessary as the main published auto-fill provider setting allows you choose Google. This is just a rear-guard action to make the public auto-fill provider selection ineffective.
I had this problem. I found that I needed to go into Chrome > Settings > Payment Methods to disable the "Save and fill payment methods" or Chrome wouldn't show the 1Password options on the onscreen keyboard.
I'm not aware of a login within Malwarebytes for Android. You're subscription is tied your Google account. Thus, as long as you're logged into the Google account you used for your premium subscription while installing Malwarebytes for Android from Google PLAY, it should load using your premium subscription. I would try uninstalling and reinstalling. Make sure you're logged into the Google account you used to purchase Malwarebytes for Android.
I am having exactly the same problem on my Pixel 4a. The password is 100% correct as I have used it to log in on two other PC's. I also have a premium account. I've logged into Malwarebytes from the android app many times in the past few years without any problems.
Thanks for the additional info and screenshot. That makes a lot more sense now. I'll ask around for an answer. In the meantime, have you tried doing the "Restore Google Play purchase" to see if it's under your Google Account?
My original password, from the website login, includes a comma. But, I experimented and figured out that the Android app's login screen does not accept commas as valid password characters, so it says my password in invalid. If I omit the comma when I enter my password, it does does not reject it as invalid (but of course it won't let me log in because the password is wrong without the comma). I'll have to change my password so it will work in both places.
Did this post not resolve your issue? If so please give us some more information so we can try and help - please remember we cannot see over your shoulder so be as descriptive as possible!
On my phone however, when opening the email, I was given a choice of using Chrome or Dropbox to open the link. I chose Chrome and dropbox gave me the message to download the dropbox app- - Chrome would not do the same on Android as it did on Windows, Again I have the dropbox app, so I then chose the Dropbox app to open the file and - I cannot enter a password, unless I could type it within about 1/2 second that the keyboard is visible.
Did this post help you? If so please give it a Like below.
Did this post fix your issue/answer your question? If so please press the 'Accept as Best Answer' button to help others find it.
Still stuck? Ask me a question! (Questions asked in the community will likely receive an answer within 4 hours!)
After I log in to a website I cannot see save password prompts after logging in on my Android phone. The prompt works fine on the same website on my computer. This happens to all websites - in fact, I have not found a website that would prompt me to save the password.
Sorry, but I must have misunderstood what you said. Can you explain a little bit more? Also, Bitwarden is the only password manager I have used in a long term basis. I have never heard of this on Android with any password manager yet. @tgreer a little help please.
Having said that, Bitwarden is still amazing especially for a free version. Also, after you use it for a while this becomes less and less of an issue. Once I had most of my website logged in and saved on a pc they do appear on Android. And for any new password on Android I just save a login with a random password before registering.
Tried a reinstall; tried 4g network, different wifi, vpn off, vpn on. It might be a coincidence but last few days the phone was refusing to fill-in any log in credentials to other apps unless i logged in to the BW app with a password first (ie it was not accepting biometric login).
For troubleshooting purposes, please check if you have enabled the Autofill using accessibility option from Enpass autofill settings in your Android device (As shown in the picture below).
If the issue persists, please share the version of the browser which you are using along with a few URL's of the webpages/apps on which you are facing this concern and I'll have this further investigated for you.
All browsers which i mentioned are latest upto this date and it is not working on apps also as i mentioned. This is really irritating that it hasn't been fixed from October. Even new password managers works perfectly in that regard.
Our dedicated team was able to reproduce the reported issue on their end. In addition, Enpass developers have confirmed that future builds will include a fix for this user-reported concern. We appreciate your patience and cooperation while we work on fixing this bug.
I'm having the same problem, when I click on my broadway bank mobile app, it no longer prompts me to use enpass. I tried enabling the Autofill using accessibility but all that did was open enpass and I have to look for the name of the institution and copy and paste the pw. I want to to work like before where all I did was put in my finger print and it would automatically fillin the info. I'm not sure if the android update broke this or it just stoped working
Security enhancements in recent versions of Android hardware, firmware, and software have all made it much more difficult to access an Android phone without the lock screen pin, password, or sequence. There are a few things you can try.
For older Android devices (4.4 KitKat or older), you can enter the incorrect pin, password, or sequence five times to be presented with a Forgot pattern/pin message. You can use your Google Account to reset the lock screen.
Did you had to wipe the device through intune and perform an enrollment via QR again? I've got the same issue. Out of the box device does not get the password prompt for the container while enrolling. When I wipe an enrolled one it gets the prompt.
I think I have found a manual work around for this.
When the device is enrolled and ready to go do the following:
Swipe the screen down twice so you can see the buttons with the functions (wifi, BT, LTE etc). Swipe right untill you see work profile. Press and hold that button. You will be transported the settings of the work container. There is a switch (on samsung) that says: Use one lock (translated from dutch). Switch this to off, setup a Pin and you have a pin active for the work container. I have set my inactivaty profile to 1 minute within intune and this seems to be enforced when I enable/setup the pin.
Then I typed in my key password but no luck on signing the APK...I even tried changing the key password using the command line keytool -keypasswd -alias cckey -keystore C:\Users\Lancelot\Desktop\release.jks. By running this I need to enter old password correctly before entering new password, which all went through; this proves that key password wasn't wrong at the first place.
I had a similar problem while updating my app. The keytool was not reading the correct keystore file and instead pointing to an older keystore file that I created months ago and not used. Searched for some solutions online but didn't find one. Almost gave up but I thought about cleaning the project by clicking Build then Clean Project. This last resort worked for me.
3a8082e126