But now I'm trying to use Passkeys in Google Chrome with Android. Unfortunately every time I try to use (or create) a Passkey only the Google Passwordmanager opens and I'm not able to use my Passkeys saved in 1Password.
I have set 1Password as my preferred app in the settings and it works fine with other apps than Google Chrome.
Currently by default Chrome and other Chromium based browsers doesn't appear to have Credential Management enabled by default. This would be required for third party password managers such as 1Password to allow you to sign in to websites using passkeys.
While we would be unable to provide a timeframe for when Google will have this enabled by default, it's possible to enable Credential Management within the Flags feature of Chrome which should allow you to use 1Password to sign into websites with passkeys. Please note, enabling and disabling particular flags can potentially lead to instability within your web browser, please ensure only the changes mentioned below are made and if you encounter any stability issues after setting these flags, please set them back to default.
If the steps above don't work, please repeat the steps again but in Step 3, please change Enable for 3rd party passkeys to Enable for Google Password Manager and 3rd party passkeys
thank you so much for the support! It works great on my phone.
Unfortunately on my tablet - for both options - Chrome just closes when trying to use a passkey. As this is an experimental feature, I want to make clear, that I don't want to complain, but rather let you know about potential issues.
1Password Version: 8.10.22
OS Version: Android 14 (X800XXU5CWL1)
Hi @BrendanR1P ,
a popup "Chrome was closed repeatedly" appears if I try it a couple of times. So it does appear like a "regular" crash, but not for 1Password. So I guess it's probably an issue with chrome - as it only appears when I activate the flags.
But if it helps, I'm happy to share my model: "Galaxy Tab S8+ SM-X800NZABEUX"
As you mentioned this only occurred when you enabled the flags, to see if there are possibly any other flags enabled which may be leading to the crash, if you open chrome://flags in your Chrome browser, would there only be the Android Credential Management for passkeys flag showing under Available with a Blue dot beside it or would there be other flags with this blue dot beside it (as shown in the screenshot below)?
The implementation is very buggy: after getting this to work once, the Autofill Options no longer had any impact, and I was able to unset that flag without issue. But it works on passkeys.io and GitHub.
@Racer77 that flag seems unrelated and could actually prevent some passkey use cases.
From the Chromium docs, it seems that this allows 3P filling eventually. The Android filling API has no support for passkeys though. Non-Google Passkey-support was added with the credential-manager API ( -in/passkeys).
So the flag with the credential-management name is more likely to work. If it works for you and not for others, then probably because you have Android 14.
@SomeBrowserDude Looked into it and that makes sense, especially since the flag and options were useless after I got it to start working at all. In any case, that flag will be expired in Chrome 123 (crbug), so it won't work soon.
@Dave_1P I did set this flag arround 2 weeks ago and it then worked in Google Chrome on my Android. But now it does not work anymore and the flag is not there anymore. Same thing in Brave on Android. The only Browser supporting 1Password Passkeys is the Samsung "Built In" one. (Since selecting 1Password for autofill passwords in the system settings. What now ?
@Dave_1P This worked in Brave for me! Using brave://flags. What a mess from Googles side!
Strangely the signin to this site here did not offer me my password. Or to any other site. Do I need to tweak other settings? Somehow this tweekeng should be done or supported with guided direct links to the settings inside the Browsee by 1Password.
Can you clarify which website you're referring to? Can you double-check that you've setup autofill to work with 1Password: Use 1Password to save logins and sign in to apps and websites on your Android device
Hopefully third-party password manager support is enabled for the Credential Manager in Chrome by their development team in the future. I recommend sending feedback to their team letting them know that you're eager to see the functionality released officially.
I need to debug CSS for some site running on the device under Android (in the common REPL mode). As I know it is possible to connect the device with the desktop via USB cable to do that. But the problem is I have no such a device (with Android). I have the Android emulator (Andy) but it seems that chrome installed on it has no dev tools at all. So is it possible to solve the problem without physical Android device?
If you were on iPhone or iPad then when you open up your bookmarks you would have to go back to where you can choose like the main menu, then you would hit the little red square with an up arrow plus on the bottom left and choose Import.
Yes, the only way on Android is to import them on your laptop/desktop and sync to Android. You have to use laptop/desktop in any case to export them right? So you can use laptop/desktop Brave and sync into Android.
Thanks everyone for your help. Actually this option of import, I think was present in the beginning for android because when I searched on Google, all procedure was written & I followed but at the end when I went back to Brave, after taking a backup of the passwords, I found that there was no option of import anymore on Android.
Unfortunate that this option is present for iPhone but not Android devices.
I will say that I have been considering switching away from Chrome/Google for some time and I find it a bit demotivating that, as soon as I make the attempt, I am stymied from completing the swap. I am traveling at the moment without access to my home computer, so I really wish Brave would allow me to import my passwords via my phone browser.
Thank you for the details description of the behavior you are seeing. I tested via the link but it looks like the webinars may be outdated. To confirm, are you saying you are able unable to join audio from the browser when using an android device? If so, can you share what version of the android device you tested with?
I wanted to provide a follow-up on this issue. Our engineering team is aware of the issue and the fix will be included in the Meeting SDK 2.9.7 release, which is expected to be released at the end of December or within the first couple weeks of January. To stay informed about this and other updates, you can visit the following link:
Hi. For some reason, Zoom stopped launching meetings through the browser in Chrome on my android. When I choose the meeting from my calendar, it will ask me to launch the meeting, and when selected, nothing happens. I uninstalled the zoom app, and now I can't finish the process of logging in because of course, it will not launch. Can someone please help?
Hi. For some reason, Zoom stopped launching meetings through the browser in Chrome on my android. When I choose the meeting from my calendar, it will ask me to launch the meeting, and when selected, nothing cure plantar fasciitis happens. I uninstalled the zoom app, and now I can't finish the process of logging in because of course, it will not launch. Can someone please help?
I'm sorry to hear that you're experiencing difficulties launching Zoom meetings through the browser on your Android device. Here are a few troubleshooting steps you can try to resolve the issue. Firstly, clear the cache and data of the Chrome browser on your device. This can help resolve any temporary issues or conflicts that may be causing the problem. If that doesn't work, try using a different browser on your Android device, such as Firefox or Microsoft Edge, to see if the issue persists. Additionally, make sure that your Chrome browser and Zoom app (if reinstalled) are both up to date. Updating the apps can help ensure compatibility and resolve any known bugs.
On a pixel 7 with up-to-date android 14, running latest Chrome 121.0.617.143,
using stock English gBoard keyboard
When editing a post, the backspace somehow seems to register as a backspace AND delete, causing lots of unintended deletion.