Autofill Accessibility on Android 11

[mdlc]

Hi!

Enpass was always working on my Galaxy S8 with Android 9. Yesterday, I installed enpass on my new S21 with Android 11, and suddenly the accessibility autofill service is no longer working. This happens with any site, for instance whe logging in to amazon.com in Chrome. I see the the Touch to Autofill notification in the adressbar, I can click it, and select Amazon, but it doesn't autofill. This happens on any site, and any app. I can see the notification, but the credentials are never filled. It only applies to the accessibility service, the regular autofill for apps that support it works. But for those that don't have this api, such as spotify, it doesn't work.

I tried disabling enabling it tens of times. I reinstalled the app a few times. Also, I ensured that enpass was not part of any battery saving measures on the device.

Tdlr; autofill by accessibility is working on older Android versions, but for the same sites and apps, doesn't work on Android 11 (OneUi 3.1)

[jddddd]

Yes, I'm having the same issue. I just created a support email to let them know as well.

 

I also cannot autofill a password in an app that is from a different site or entry in the enpass

[Pratyush Sharma]

Hi @mdlc @jddddd

Welcome to the forums!

We have taken note of this and our team is now analyzing into the issue.

Thanks for your co-operation.

[jnyer1227]

I also am having same issue on S21 Ultra with android 11

[Pratyush Sharma]

Hi @mdlc @jddddd @jnyer1227,

Sorry for the inconvenience.

Our QA team is not able to reproduce the issue can you please let us know the following details so we can further investigate:

• Which Enpass version are you using?
• Share the screenshot of your Enpass Autofill setting?
• If possible ,share the video of the issue? It will help in a clear understanding of the problem before further proceedings.

Thanks!

[mdlc]

Enpass: 6.6.1.449

OS: Android (11), OneUI 3.1

Can't take screenshots within Enpass, but can take screenshots of the system accessibility settings

[Pratyush Sharma]

Hi @mdlc,

To take a screenshot in the Enpass app, please follow the below steps:

• Open Enpass app --> Goto Setting --> Advanced --> Enable Allow Screenshots.

Thanks!

[mdlc]

As you requested 

[Garima Singh]

Hey @mdlc

Thanks for sharing this. We'll look into this issue at our end and will get back to you soon.

[itservicesx]

Hi, I can confirm that this issue also exists on my Galaxy S21 running One UI 3.1, based on Android 11. I believe this issue may be exclusive to Samsung devices running One UI 3 or One UI 3.1.

I hope the team can sort this problem out asap as it's very frustrating to see that I am unable to autofill via accessibility service on my new phone.

Many thanks

[Garima Singh]

Hey @itservicesx & @mdlc

Thanks for sharing the inputs. For further testing, could you please disable 'Android auto-fill service' from the Enpass Browser settings and then enable the 'Auto-fill using accessibility'. Now try to auto-fill again on the same device and and share your findings with us.

[mdlc]

On 2/23/2021 at 12:35 PM, Garima Singh said:

Hey @itservicesx & @mdlc

Thanks for sharing the inputs. For further testing, could you please disable 'Android auto-fill service' from the Enpass Browser settings and then enable the 'Auto-fill using accessibility'. Now try to auto-fill again on the same device and and share your findings with us.

Hi! I tried this, but it only makes things worse, since it disables the autofill for native forms, but it still doesn't work in the browser as described.

[Garima Singh]

Hey @mdlc

We have fixed similar issues of auto-fill on Samsung s21 and the beta version for same is in pipeline. Please wait for the stable version to be released hopefully in next week.

Thanks!

[Eduardo P.]

Hi all,

Don't mean to pour fuel on the fire but I can confirm this also happens on my S10+ with OneUI 3.0. I'm keeping my fingers crossed for the next stable version to fix this.

Thanks!

 

[Pratyush Sharma]

Hi All,

We've released an updated version of Enpass in which we have fixed this issue. We would appreciate if you could share your feedback on the latest version. Thanks!