kellybrf

On 12/4/2020 at 7:53 AM, Garima Singh said:

Hey @kellybrf

Thanks for the suggestion. However, I would like to share that you can can try auto-filling using the Accessibility service, for this please perform these simple steps.

1. Open the Chromebook device.
2. Go to settings --> click on Accessibility.
3. Enable for Enpass.
4. Now open any website in brave browser where he want to auto-fill.
5. Enpass notification will appear in the Chromebook Notification bar.
6. Click on Enpass notification icon and try to auto-fill.

Hope this helps!

 

Sorry, I thought I had replied to this?  Chrome OS does not have this accessibility option like Android does, so this work-around does not work.

For those of us not using Chrome on our Chrome OS devices can the Android autofill service option be added? I use a Chromebook Duet mainly as a tablet and am using Brave as my browser, which is available only as an Android app, but Enpass does not seem to have a way to talk to the browser.

6 hours ago, Garima Singh said:

Hi @kellybrf

Could you please share the device on which you are getting this option along with Enpass version you using on the same device?

Thanks.

I'm using a Pixel 4XL, my Enpass version is 6.4.0.322

edit, it's also available for me on Windows 6.4.0 (631)

6 hours ago, Garima Singh said:

Hi @kellybrf

Thanks for using Enpass and writing to us. Our team has already started working on the exclude passwords implementation. I guess, we'll have to wait till this is released in the upcoming versions.

I already have the exclude symbol option, what are they working on?

I was just coming to post this same request! I almost always have to edit my generated passwords because the site lists included symbols, not excluded ones

got my p4xl yesterday and I can confirm that the face unlock works very well with the beta, but I would also second an option to skip the confirmation step.  it seems unnecessary

On 2/26/2019 at 6:59 AM, Anshu kumar said:

Hey guys,

Enpass 6 for Chromebook is under the development phase. But sorry to say at the moment I can't specify any ETA.

Thanks for your understanding.

We're now going on 5 months since we were told it was coming soon. Some transparency in the process would be appreciated, especially since this is an app many paid for specifically because it offered Chromebook support, only to have it removed.

I'm experiencing this issue again.  Some background, this is my wife's account which was set up late last year but she hadn't used it much.  When I first set it up I was having sync issues, found this thread, enrolled her in beta and all was good.  Her previous pw manager license expired last week so she started using Enpass but it was asking for her master pw, which wasn't being accepted on either the Android or Win10 desktop app, which was an oddity to begin with.  I still had her old .CSV file so I deleted the Enpass on both and set her up fresh.  Win10 client seems to be working fine, but it's not syncing to her phone via Google Drive.  I deleted the old Enpass folder in Drive before setting the account up again.  She's using a Pixel 2 running stock Androids 8.1.  When I initially link the Drive account via the Android app it says it syncs, though no data actually comes through.  That initial link is the Last Synchronized time; the Last Attempt updates with every try but it doesn't actually sync.  There is no error given.