toriigate

toriigate

I can confirm that Opera 79 does not work with any of my usual password managers (despite the claim in your changelog), and still doesn't seem to support the native Android autofill API.

Tried with: 1Password; Bitwarden.

toriigate

I've raised this as a bug relating to the latest version of Opera for Android, ref. OFABUGS-4534

See also: https://forums.opera.com/topic/68738/personalize-your-browsing-with-dynamic-wallpapers-in-opera-for-android-version-79

toriigate

Submitted bug report ref. OFABUGS-4534

toriigate

@iamawais55 If you read my previous posts, it's still hit or miss. Most password don't seem to be working yet, only RF.

toriigate

@leocg From the current listing in the Google Play Store.

Screenshot_20231226_232558_Google Play Store.jpg

toriigate

Interesting yet random.

toriigate

Interesting yet random.

toriigate

@iamawais55 If you read my previous posts, it's still hit or miss. Most password don't seem to be working yet, only RF.

toriigate

@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...

toriigate

@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?

toriigate

@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?

toriigate

@xvegadev Maybe this trick used to work on Android 13, but it definitely doesn't work anymore on version 14.

toriigate