Native Android auto-fill support
-
-
XVega last edited by XVega
@toriigate I've just tried wit latest version of opera, 75.5.4195.76987 on a pixel7a running latest beta of android AP11.231215.007 with our product RoboForm (v. 9.5.4.18 latest), and autofill seems to be working even without the trick!
-
toriigate last edited by
@xvega Latest version of Opera for Android is 79.4.4195.76850 (https://play.google.com/store/apps/details?id=com.opera.browser).
Does RoboForm use the native Android autofill API, or does it leverage the accessibility function?
-
XVega last edited by XVega
@toriigate yes, https://play.google.com/store/apps/details?id=com.opera.browser I get latest version 79.5.4195.76987 released on Jan 11, although I'm not in beta program, maybe they did a staged rollout (only a percent of users get the latest release). RoboForm uses only Native Autofill API.
-
toriigate last edited by
@xvega I am very confused now. I've tried literally all the other major password managers on the market (1Password, Bitwarden, Keeper, Dashlane and Enpass) and none of them work with Opera through the autofill API... Did you do anything unusual or different when you implemented this functionality in RoboForm?
-
iamawais55 Banned last edited by
@achappel Opera for Android had not fully integrated with Android's native auto-fill feature.
-
toriigate last edited by
@iamawais55 And yet, I have just tried @XVega 's suggestion and RoboForm does seem to work fine in Opera through native autofill and NO accessibility enabled...
-
iamawais55 Banned last edited by
@toriigate
It's great to hear. Opera may be improving its compatibility with password managers. I have to stay connected with recent updates. -
toriigate last edited by
@iamawais55 If you read my previous posts, it's still hit or miss. Most password don't seem to be working yet, only RF.
-
hyesun1 last edited by
Still not working now, at least with Microsoft Authenticator. Is there any plan to fix this?
