[GH-ISSUE #895] [Android] Auto-fill doesn't work on Samsung browser Stable and Beta. #49091

New Issue

Closed

opened 2026-05-01 07:55:02 -05:00 by GiteaMirror · 77 comments

GiteaMirror commented 2026-05-01 07:55:02 -05:00

Owner

Copy Link

Originally created by @the4anoni on GitHub (May 10, 2020).
Original GitHub issue: https://github.com/bitwarden/android/issues/895

Originally assigned to: @mpbw2 on GitHub.

Describe the Bug

Like in topic

Steps To Reproduce

Try to login via auto-fill on Samsung browser.

Expected Result

Bitwarden auto-fill suggest you to fill passwords.

Actual Result

There isn't suggestion to auto-fill login and password

Screenshots or Video

Environment

• Device: Samsung Galaxy S10
• Operating system: Android Q OneUI 2.1
• App Build Version: 2.3.1 (2413)

Originally created by @the4anoni on GitHub (May 10, 2020). Original GitHub issue: https://github.com/bitwarden/android/issues/895 Originally assigned to: @mpbw2 on GitHub. ## Describe the Bug Like in topic ## Steps To Reproduce Try to login via auto-fill on Samsung browser. ## Expected Result Bitwarden auto-fill suggest you to fill passwords. ## Actual Result There isn't suggestion to auto-fill login and password ## Screenshots or Video  ## Environment - Device: Samsung Galaxy S10 - Operating system: Android Q OneUI 2.1 - App Build Version: 2.3.1 (2413)

GiteaMirror closed this issue 2026-05-01 07:55:03 -05:00

GiteaMirror commented 2026-05-01 07:55:08 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (May 13, 2020):

Samsung released an updated browser beta today which properly allows both the autofill service and our autofill accessibility service to function.

<!-- gh-comment-id:627711074 --> @mpbw2 commented on GitHub (May 13, 2020): Samsung released an updated browser beta today which properly allows both the autofill service and our autofill accessibility service to function.

GiteaMirror commented 2026-05-01 07:55:10 -05:00

Author

Owner

Copy Link

@dardaner commented on GitHub (May 13, 2020):

I can't make it work automatic filling

• I have installed the latest beta version of Samsung Internet
• I installed the latest version of Bitwarden
  But Bitwarden autofill on Android 10 still doesn't work

<!-- gh-comment-id:627762424 --> @dardaner commented on GitHub (May 13, 2020): I can't make it work automatic filling - I have installed the latest beta version of Samsung Internet - I installed the latest version of Bitwarden But Bitwarden autofill on Android 10 still doesn't work

GiteaMirror commented 2026-05-01 07:55:11 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (May 13, 2020):

Autofill also doesn't work for me, I have latest Bitwarden and tried on latest S Browser Beta

<!-- gh-comment-id:627768650 --> @the4anoni commented on GitHub (May 13, 2020): Autofill also doesn't work for me, I have latest Bitwarden and tried on latest S Browser Beta

GiteaMirror commented 2026-05-01 07:55:14 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (May 13, 2020):

Beta version 12.0.1.4 is working with both accessibility and autofill service (though their autofill service values are a bit strange - give the beta more time to cook).

Edit: Forgot to mention this is with the latest Bitwarden beta as well - I apologize if that was the source of the confusion.

<!-- gh-comment-id:627975353 --> @mpbw2 commented on GitHub (May 13, 2020): Beta version 12.0.1.4 is working with both accessibility and autofill service (though their autofill service values are a bit strange - give the beta more time to cook). Edit: Forgot to mention this is with the latest Bitwarden beta as well - I apologize if that was the source of the confusion. 

GiteaMirror commented 2026-05-01 07:55:15 -05:00

Author

Owner

Copy Link

@dardaner commented on GitHub (May 13, 2020):

Hello
thank you for your reply
Where can we find the beta versions of Bitwarden and Samsung Internet Browser 12.0.1.4
Do you have any links please?
Thank you

<!-- gh-comment-id:628091172 --> @dardaner commented on GitHub (May 13, 2020): Hello thank you for your reply Where can we find the beta versions of Bitwarden and Samsung Internet Browser 12.0.1.4 Do you have any links please? Thank you

GiteaMirror commented 2026-05-01 07:55:15 -05:00

Author

Owner

Copy Link

@dardaner commented on GitHub (May 13, 2020):

It's good it works, THANKS: +1:
i found on apk mirror
For those who are interested
https://www.apkmirror.com/apk/samsung-electronics-co-ltd/samsung-internet-beta/samsung-internet-beta-12-0-1-4-release/

for me it works with Bitwarden 2.3.1 official version, without beta version
but with Samsung Internet Browser Beta 12.0.1.4

<!-- gh-comment-id:628105587 --> @dardaner commented on GitHub (May 13, 2020): It's good it works, THANKS: +1: i found on apk mirror For those who are interested https://www.apkmirror.com/apk/samsung-electronics-co-ltd/samsung-internet-beta/samsung-internet-beta-12-0-1-4-release/ for me it works with Bitwarden 2.3.1 official version, without beta version but with Samsung Internet Browser Beta 12.0.1.4

GiteaMirror commented 2026-05-01 07:55:19 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (May 13, 2020):

It's also available on the Play Store as a separate installation:

https://play.google.com/store/apps/details?id=com.sec.android.app.sbrowser.beta

<!-- gh-comment-id:628108445 --> @mpbw2 commented on GitHub (May 13, 2020): It's also available on the Play Store as a separate installation: https://play.google.com/store/apps/details?id=com.sec.android.app.sbrowser.beta

GiteaMirror commented 2026-05-01 07:55:22 -05:00

Author

Owner

Copy Link

@dardaner commented on GitHub (May 13, 2020):

do you have a link for Bitwarden in beta version? I can't find it
Thank you

<!-- gh-comment-id:628112163 --> @dardaner commented on GitHub (May 13, 2020): do you have a link for Bitwarden in beta version? I can't find it Thank you

GiteaMirror commented 2026-05-01 07:55:26 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (May 13, 2020):

For Bitwarden use the 'join beta' button on our Play Store page and your existing installation will be upgraded.

<!-- gh-comment-id:628159552 --> @mpbw2 commented on GitHub (May 13, 2020): For Bitwarden use the 'join beta' button on our Play Store page and your existing installation will be upgraded.

GiteaMirror commented 2026-05-01 07:55:28 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (May 18, 2020):

Auto fill doesn't works for me
Bitwarden app version: 2.3.1 (2413)
I am Bitwarden beta tester.

<!-- gh-comment-id:630242304 --> @the4anoni commented on GitHub (May 18, 2020): Auto fill doesn't works for me Bitwarden app version: 2.3.1 (2413) I am Bitwarden beta tester. 

GiteaMirror commented 2026-05-01 07:55:30 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (May 20, 2020):

@mportune-bw I also tried v11.1.2.2 but it also doesn't work

<!-- gh-comment-id:631631239 --> @the4anoni commented on GitHub (May 20, 2020): @mportune-bw I also tried v11.1.2.2 but it also doesn't work

GiteaMirror commented 2026-05-01 07:55:31 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (May 20, 2020):

@the4anoni It definitely requires the newer v12.x.x.x release, but unfortunately I'm not sure why that isn't even working for you when it works for others (as well as myself). Maybe something else on your device is interfering with autofill and/or accessibility?

<!-- gh-comment-id:631664433 --> @mpbw2 commented on GitHub (May 20, 2020): @the4anoni It definitely requires the newer v12.x.x.x release, but unfortunately I'm not sure why that isn't even working for you when it works for others (as well as myself). Maybe something else on your device is interfering with autofill and/or accessibility?

GiteaMirror commented 2026-05-01 07:55:33 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (May 20, 2020):

@the4anoni It definitely requires the newer v12.x.x.x release, but unfortunately I'm not sure why that isn't even working for you when it works for others (as well as myself). Maybe something else on your device is interfering with autofill and/or accessibility?

Auto fill works on chrome

<!-- gh-comment-id:631670758 --> @the4anoni commented on GitHub (May 20, 2020): > @the4anoni It definitely requires the newer v12.x.x.x release, but unfortunately I'm not sure why that isn't even working for you when it works for others (as well as myself). Maybe something else on your device is interfering with autofill and/or accessibility? Auto fill works on chrome

GiteaMirror commented 2026-05-01 07:55:35 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (May 20, 2020):

Did you check the settings in v12? Settings > Privacy and security > Autofill forms

<!-- gh-comment-id:631673049 --> @mpbw2 commented on GitHub (May 20, 2020): Did you check the settings in v12? `Settings > Privacy and security > Autofill forms`

GiteaMirror commented 2026-05-01 07:55:36 -05:00

Author

Owner

Copy Link

@OJ7 commented on GitHub (May 21, 2020):

Did you check the settings in v12? Settings > Privacy and security > Autofill forms

Tried with this enabled/disabled and still not working on latest beta for both apps.
Also tried disabling the options under Usernames and Passwords to see if that made any difference but no luck.

<!-- gh-comment-id:632017406 --> @OJ7 commented on GitHub (May 21, 2020): > Did you check the settings in v12? `Settings > Privacy and security > Autofill forms` Tried with this enabled/disabled and still not working on latest beta for both apps. Also tried disabling the options under Usernames and Passwords to see if that made any difference but no luck.

GiteaMirror commented 2026-05-01 07:55:37 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (May 21, 2020):

I'm at a loss. I'll keep an eye out for any clues as to why it's not working for you, but for the moment... /shrug

<!-- gh-comment-id:632135526 --> @mpbw2 commented on GitHub (May 21, 2020): I'm at a loss. I'll keep an eye out for any clues as to why it's not working for you, but for the moment... /shrug

GiteaMirror commented 2026-05-01 07:55:40 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (May 22, 2020):

Did you check the settings in v12? Settings > Privacy and security > Autofill forms

I had enabled this, but auto fill still doesn't work.
Samsung Internet 12.0.1.17 beta

<!-- gh-comment-id:632492211 --> @the4anoni commented on GitHub (May 22, 2020): > Did you check the settings in v12? `Settings > Privacy and security > Autofill forms` I had enabled this, but auto fill still doesn't work. Samsung Internet 12.0.1.17 beta

GiteaMirror commented 2026-05-01 07:55:44 -05:00

Author

Owner

Copy Link

@MatyCZ commented on GitHub (May 22, 2020):

I have the same problem, autofill doesn`t work in Samsung Internet. Tried enable/disable some options in Setting and still not working.

Autofill works in Edge and Chrome on same device.

Bitwarden Beta 2.3.1 (2413)
Samsung Internet Beta 12.0.1.17

<!-- gh-comment-id:632530850 --> @MatyCZ commented on GitHub (May 22, 2020): I have the same problem, autofill doesn`t work in Samsung Internet. Tried enable/disable some options in Setting and still not working. Autofill works in Edge and Chrome on same device. Bitwarden Beta 2.3.1 (2413) Samsung Internet Beta 12.0.1.17

GiteaMirror commented 2026-05-01 07:55:48 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (May 25, 2020):

@mportune-bw can you re-open issue?

<!-- gh-comment-id:633463681 --> @the4anoni commented on GitHub (May 25, 2020): @mportune-bw can you re-open issue?

GiteaMirror commented 2026-05-01 07:55:50 -05:00

Author

Owner

Copy Link

@dardaner commented on GitHub (May 26, 2020):

With me it works
Not always 100%, but it works when it wants
Some sites are not working well yet, automatic detection is not always reactive

Conditions for it to work

• install Bitwarden 2.3.1 on PlayStore
• install Samsung Browser Beta 12.0.1.17 on APK mirror
• I use Gboard the Google keyboard
• In Parameters / System / Language and input / Automatic input service: Select Bitwarden
• Being on Android 10
• Activate the filling and accessibility options on Bitwarden
• In the Settings of Samsung Browser,
  1 .Settings / Useful functions / Authorized applications / Bitwarden ACTIVE

2. Parameters / Confidentiality and security / Automatic filling of ACTIVE forms

<!-- gh-comment-id:633978279 --> @dardaner commented on GitHub (May 26, 2020): With me it works Not always 100%, but it works when it wants Some sites are not working well yet, automatic detection is not always reactive Conditions for it to work - install Bitwarden 2.3.1 on PlayStore - install Samsung Browser Beta 12.0.1.17 on APK mirror - I use Gboard the Google keyboard - In Parameters / System / Language and input / Automatic input service: Select Bitwarden - Being on Android 10 - Activate the filling and accessibility options on Bitwarden - In the Settings of Samsung Browser, 1 .Settings / Useful functions / Authorized applications / Bitwarden ACTIVE 2. Parameters / Confidentiality and security / Automatic filling of ACTIVE forms

GiteaMirror commented 2026-05-01 07:55:51 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (May 26, 2020):

With me it works
Not always 100%, but it works when it wants
Some sites are not working well yet, automatic detection is not always reactive

Conditions for it to work

• install Bitwarden 2.3.1 on PlayStore
• install Samsung Browser Beta 12.0.1.17 on APK mirror
• I use Gboard the Google keyboard
• In Parameters / System / Language and input / Automatic input service: Select Bitwarden
• Being on Android 10
• Activate the filling and accessibility options on Bitwarden
• In the Settings of Samsung Browser,
  1 .Settings / Useful functions / Authorized applications / Bitwarden ACTIVE

1. Parameters / Confidentiality and security / Automatic filling of ACTIVE forms

Can you give one example site on which auto fill works?

<!-- gh-comment-id:634144838 --> @the4anoni commented on GitHub (May 26, 2020): > With me it works > Not always 100%, but it works when it wants > Some sites are not working well yet, automatic detection is not always reactive > > Conditions for it to work > > * install Bitwarden 2.3.1 on PlayStore > * install Samsung Browser Beta 12.0.1.17 on APK mirror > * I use Gboard the Google keyboard > * In Parameters / System / Language and input / Automatic input service: Select Bitwarden > * Being on Android 10 > * Activate the filling and accessibility options on Bitwarden > * In the Settings of Samsung Browser, > 1 .Settings / Useful functions / Authorized applications / Bitwarden ACTIVE > > 1. Parameters / Confidentiality and security / Automatic filling of ACTIVE forms Can you give one example site on which auto fill works?

GiteaMirror commented 2026-05-01 07:55:52 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (May 30, 2020):

Try this.

1. Enter the address below in the url text box of the Samsung browser
   internet://flags/#force-renderer-accessibility
2. Change WebAccessibility to enable and then restart browser
3. That could work.

• Please upgrade Samsung browser and bitwarden to beta.

p.s. Sorry I can't speak English. I wrote it with a translator.

Doesn't work for me, tried on last SBrowser beta and Bitwarden last beta.

<!-- gh-comment-id:636313861 --> @the4anoni commented on GitHub (May 30, 2020): > Try this. > > 1. Enter the address below in the url text box of the Samsung browser > internet://flags/#force-renderer-accessibility > 2. Change WebAccessibility to enable and then restart browser > 3. That could work. > > * Please upgrade Samsung browser and bitwarden to beta. > > p.s. Sorry I can't speak English. I wrote it with a translator. Doesn't work for me, tried on last SBrowser beta and Bitwarden last beta.

GiteaMirror commented 2026-05-01 07:55:53 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (Jun 9, 2020):

Sbrowser beta 12.0.1.36 and bitwarden 2.4.3, autofill still doesn't work @mportune-bw

<!-- gh-comment-id:641529584 --> @the4anoni commented on GitHub (Jun 9, 2020): Sbrowser beta 12.0.1.36 and bitwarden 2.4.3, autofill still doesn't work @mportune-bw

GiteaMirror commented 2026-05-01 07:55:55 -05:00

Author

Owner

Copy Link

@anuraag488 commented on GitHub (Jun 10, 2020):

Sbrowser beta 12.0.1.36 and bitwarden 2.4.3, autofill still doesn't work @mportune-bw

Working fine here

<!-- gh-comment-id:641916804 --> @anuraag488 commented on GitHub (Jun 10, 2020): > Sbrowser beta 12.0.1.36 and bitwarden 2.4.3, autofill still doesn't work @mportune-bw Working fine here

GiteaMirror commented 2026-05-01 07:55:56 -05:00

Author

Owner

Copy Link

@anuraag488 commented on GitHub (Jun 13, 2020):

It doesn't work fine. For example google account sign in. I would suggest to implement a keyboard for such cases.
https://github.com/bitwarden/mobile/issues/62

<!-- gh-comment-id:643569767 --> @anuraag488 commented on GitHub (Jun 13, 2020): It doesn't work fine. For example google account sign in. I would suggest to implement a keyboard for such cases. https://github.com/bitwarden/mobile/issues/62

GiteaMirror commented 2026-05-01 07:55:57 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (Jun 13, 2020):

Now it works for me :)

<!-- gh-comment-id:643603619 --> @the4anoni commented on GitHub (Jun 13, 2020):  Now it works for me :)

GiteaMirror commented 2026-05-01 07:55:59 -05:00

Author

Owner

Copy Link

@anuraag488 commented on GitHub (Jun 13, 2020):

@the4anoni clicking on that fills password not email address.

<!-- gh-comment-id:643606527 --> @anuraag488 commented on GitHub (Jun 13, 2020): @the4anoni clicking on that fills password not email address.

GiteaMirror commented 2026-05-01 07:56:00 -05:00

Author

Owner

Copy Link

@the4anoni commented on GitHub (Jun 13, 2020):

@the4anoni clicking on that fills password not email address.

Only on google.com, on github it works ok.

Also on chrome I've noticed this same bug.

<!-- gh-comment-id:643610130 --> @the4anoni commented on GitHub (Jun 13, 2020): > @the4anoni clicking on that fills password not email address. Only on google.com, on github it works ok. Also on chrome I've noticed this same bug.

GiteaMirror commented 2026-05-01 07:56:01 -05:00

Author

Owner

Copy Link

@OJ7 commented on GitHub (Jul 1, 2020):

Auto fill seems to finally work now after the most recent Samsung Internet (not beta) update.

<!-- gh-comment-id:652198142 --> @OJ7 commented on GitHub (Jul 1, 2020): Auto fill seems to finally work now after the most recent Samsung Internet (not beta) update.

GiteaMirror commented 2026-05-01 07:56:04 -05:00

Author

Owner

Copy Link

@alksjd commented on GitHub (Jul 27, 2020):

Auto fill seems to finally work now after the most recent Samsung Internet (not beta) update.

I get the auto-fill option but clicking on it doesn't give me respective login details instead I get this prompt 'there are no items in you vault for com.sec.android.app.sbrowser.beta'.

<!-- gh-comment-id:664178719 --> @alksjd commented on GitHub (Jul 27, 2020): > Auto fill seems to finally work now after the most recent Samsung Internet (not beta) update. I get the auto-fill option but clicking on it doesn't give me respective login details instead I get this prompt 'there are no items in you vault for com.sec.android.app.sbrowser.beta'.

GiteaMirror commented 2026-05-01 07:56:07 -05:00

Author

Owner

Copy Link

@raghusundaram commented on GitHub (Aug 2, 2020):

Auto fill seems to finally work now after the most recent Samsung Internet (not beta) update.

Can you please report back the exact version number ?

<!-- gh-comment-id:667650249 --> @raghusundaram commented on GitHub (Aug 2, 2020): > Auto fill seems to finally work now after the most recent Samsung Internet (not beta) update. Can you please report back the exact version number ?

GiteaMirror commented 2026-05-01 07:56:09 -05:00

Author

Owner

Copy Link

@raghusundaram commented on GitHub (Aug 2, 2020):

I want to make it clear the problem some people face in using the Auto-fill service using the accessibility feature.

Don't try to use Bitwarden with any browsers in Android until and unless it natively surfaces Bitwarden using Android Autofill API.
Forcing the browsers to integrate with Bitwarden using accessibility service would be useless.
As Bitwarden can only know the application name using accessibility service and not the website URL.
In that case, it would offer incorrect choices.

Instead you can use Bitwarden with any apps such as Instagram, or your banking app in Android.
As in this case, Bitwarden just needs to know the application name alone.

<!-- gh-comment-id:667651034 --> @raghusundaram commented on GitHub (Aug 2, 2020): I want to make it clear the problem some people face in using the Auto-fill service using the accessibility feature. Don't try to use Bitwarden with any browsers in Android until and unless it natively surfaces Bitwarden using Android Autofill API. Forcing the browsers to integrate with Bitwarden using accessibility service would be useless. As Bitwarden can only know the application name using accessibility service and not the website URL. In that case, it would offer incorrect choices. Instead you can use Bitwarden with any apps such as Instagram, or your banking app in Android. As in this case, Bitwarden just needs to know the application name alone.

GiteaMirror commented 2026-05-01 07:56:13 -05:00

Author

Owner

Copy Link

@aaronstc1 commented on GitHub (Aug 14, 2020):

For me auto fill "works" but it just sees Samsung Browser as an app and won't show me webpage log ins like in chrome.

<!-- gh-comment-id:674279106 --> @aaronstc1 commented on GitHub (Aug 14, 2020): For me auto fill "works" but it just sees Samsung Browser as an app and won't show me webpage log ins like in chrome.

GiteaMirror commented 2026-05-01 07:56:19 -05:00

Author

Owner

Copy Link

@raghusundaram commented on GitHub (Aug 15, 2020):

For me auto fill "works" but it just sees Samsung Browser as an app and won't show me webpage log ins like in chrome.

Please refer my previous comment.
I have given a clear explanation.

<!-- gh-comment-id:674356642 --> @raghusundaram commented on GitHub (Aug 15, 2020): > For me auto fill "works" but it just sees Samsung Browser as an app and won't show me webpage log ins like in chrome. Please refer my previous comment. I have given a clear explanation.

GiteaMirror commented 2026-05-01 07:56:26 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Sep 1, 2020):

Any updates on this? As mentioned above, accessibility services is NOT an option for using with this browser. I have moved to opera, untill this get fixed

<!-- gh-comment-id:685027888 --> @yurividal commented on GitHub (Sep 1, 2020): Any updates on this? As mentioned above, accessibility services is NOT an option for using with this browser. I have moved to opera, untill this get fixed

GiteaMirror commented 2026-05-01 07:56:30 -05:00

Author

Owner

Copy Link

@ghost commented on GitHub (Dec 24, 2020):

I'm having major issues with the autofill service in Samsung Internet for a long time now. Is there any more information on this @mportune-bw?

<!-- gh-comment-id:750937846 --> @ghost commented on GitHub (Dec 24, 2020): I'm having major issues with the autofill service in Samsung Internet for a long time now. Is there any more information on this @mportune-bw?

GiteaMirror commented 2026-05-01 07:56:31 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Dec 24, 2020):

I'm having major issues with the autofill service in Samsung Internet for a long time now. Is there any more information on this @mportune-bw?

As far as I understand, Samsung is not too committed to implementing this on their browser, since they rather push users to their own Samsung Pass. But, maybe when they upgrade their chromium base in future builds this might get inherited.
I have tried to reach many of Samsung browser's devs on their Twitter and their Blog, and on Samsung forums, about this, but I am always ignored.

<!-- gh-comment-id:750939992 --> @yurividal commented on GitHub (Dec 24, 2020): > I'm having major issues with the autofill service in Samsung Internet for a long time now. Is there any more information on this @mportune-bw? As far as I understand, Samsung is not too committed to implementing this on their browser, since they rather push users to their own Samsung Pass. But, maybe when they upgrade their chromium base in future builds this might get inherited. I have tried to reach many of Samsung browser's devs on their Twitter and their Blog, and on Samsung forums, about this, but I am always ignored.

GiteaMirror commented 2026-05-01 07:56:32 -05:00

Author

Owner

Copy Link

@ghost commented on GitHub (Dec 24, 2020):

I'm having major issues with the autofill service in Samsung Internet for a long time now. Is there any more information on this @mportune-bw?

As far as I understand, Samsung is not too committed to implementing this on their browser, since they rather push users to their own Samsung Pass. But, maybe when they upgrade their chromium base in future builds this might get inherited.
I have tried to reach many of Samsung browser's devs on their Twitter and their Blog, and on Samsung forums, about this, but I am always ignored.

Damn, that is extremely unfortunate. Hopefully they'll fully embrace the autofill framework to push more users to their browser.

<!-- gh-comment-id:750945151 --> @ghost commented on GitHub (Dec 24, 2020): > > I'm having major issues with the autofill service in Samsung Internet for a long time now. Is there any more information on this @mportune-bw? > > As far as I understand, Samsung is not too committed to implementing this on their browser, since they rather push users to their own Samsung Pass. But, maybe when they upgrade their chromium base in future builds this might get inherited. > I have tried to reach many of Samsung browser's devs on their Twitter and their Blog, and on Samsung forums, about this, but I am always ignored. Damn, that is extremely unfortunate. Hopefully they'll fully embrace the autofill framework to push more users to their browser.

GiteaMirror commented 2026-05-01 07:56:34 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Apr 18, 2021):

@mportune-bw i found out when it stops working and what to do as a workaround to make it work again. When I go to the tab view in Samsung internet and open a new tab, i go to the login page of that particular website, and bitwarden doesn't work. When I close the samsung internet app and re-open it. It starts loading the login page of that particular website again and voila, bitwarden works.

Test scenario 2: when i open two new tabs with two different websited and go to the login pages of both websites, close samsung internet and reopen the app, then bitwarden works on both tabs. I can switch between the tabs and it remains working. When I close one of the two and the other one remains working until both tabs are closed and obviously to browse you need a new tab.

So, workaround for now is: when I reach a login page, close samsung internet and reopen. Even though this workaround works 100% of the time for me, it has become slightly annoying that I have to keep doing this. Is this a bitwarden or samsung internet app issue?

Versions
Bitwarden: Version: 2.9.1 (3444)
Samsung Internet: 14.0.1.62

Edit: also raised an issue with samsung regarding samsung internet app. So both parties can have a look at it. It seems to be more of an issue with Samsung Internet app than Bitwarden. As if theres a bug how Samsung Internet allows third party apps to use the auto fill feature. Because Bitwarden works fine on other browser apps (chrome, brave and above confirmed by other users: firefox etc)

<!-- gh-comment-id:822058758 --> @Tosko4 commented on GitHub (Apr 18, 2021): @mportune-bw i found out when it stops working and what to do as a workaround to make it work again. When I go to the tab view in Samsung internet and open a new tab, i go to the login page of that particular website, and bitwarden doesn't work. When I close the samsung internet app and re-open it. It starts loading the login page of that particular website again and voila, bitwarden works. Test scenario 2: when i open two new tabs with two different websited and go to the login pages of both websites, close samsung internet and reopen the app, then bitwarden works on both tabs. I can switch between the tabs and it remains working. When I close one of the two and the other one remains working until both tabs are closed and obviously to browse you need a new tab. So, workaround for now is: when I reach a login page, close samsung internet and reopen. Even though this workaround works 100% of the time for me, it has become slightly annoying that I have to keep doing this. Is this a bitwarden or samsung internet app issue? Versions Bitwarden: Version: 2.9.1 (3444) Samsung Internet: 14.0.1.62 Edit: also raised an issue with samsung regarding samsung internet app. So both parties can have a look at it. It seems to be more of an issue with Samsung Internet app than Bitwarden. As if theres a bug how Samsung Internet allows third party apps to use the auto fill feature. Because Bitwarden works fine on other browser apps (chrome, brave and above confirmed by other users: firefox etc)

GiteaMirror commented 2026-05-01 07:56:35 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Apr 19, 2021):

@mportune-bw i found out when it stops working and what to do as a workaround to make it work again. When I go to the tab view in Samsung internet and open a new tab, i go to the login page of that particular website, and bitwarden doesn't work. When I close the samsung internet app and re-open it. It starts loading the login page of that particular website again and voila, bitwarden works.

Test scenario 2: when i open two new tabs with two different websited and go to the login pages of both websites, close samsung internet and reopen the app, then bitwarden works on both tabs. I can switch between the tabs and it remains working. When I close one of the two and the other one remains working until both tabs are closed and obviously to browse you need a new tab.

So, workaround for now is: when I reach a login page, close samsung internet and reopen. Even though this workaround works 100% of the time for me, it has become slightly annoying that I have to keep doing this. Is this a bitwarden or samsung internet app issue?

Versions
Bitwarden: Version: 2.9.1 (3444)
Samsung Internet: 14.0.1.62

Edit: also raised an issue with samsung regarding samsung internet app. So both parties can have a look at it. It seems to be more of an issue with Samsung Internet app than Bitwarden. As if theres a bug how Samsung Internet allows third party apps to use the auto fill feature. Because Bitwarden works fine on other browser apps (chrome, brave and above confirmed by other users: firefox etc)

So response from Samsung is as expected utterly useless!! Or the support agent didn't take the time to really read my error description or lack the knowledge to think and see the bigger picture. Their response was:

Dear Customer,

Thank you for contacting us. We appreciate the opportunity to assist you.

I understand you wish to use third party apps. Since we are not directly afilitated we can offer no assistance in this regard. Samsung will not change the browser for a company they have no partnerships with.

Also know that you might receive a short survey regarding our interaction. Please take a few seconds to it fill out it would greatly help us improve our customer support experience!

I have sent a new inquiry to have them read my problem description again and try to think along. Or is there something you can do without their support @mportune-bw

<!-- gh-comment-id:822217867 --> @Tosko4 commented on GitHub (Apr 19, 2021): > @mportune-bw i found out when it stops working and what to do as a workaround to make it work again. When I go to the tab view in Samsung internet and open a new tab, i go to the login page of that particular website, and bitwarden doesn't work. When I close the samsung internet app and re-open it. It starts loading the login page of that particular website again and voila, bitwarden works. > > Test scenario 2: when i open two new tabs with two different websited and go to the login pages of both websites, close samsung internet and reopen the app, then bitwarden works on both tabs. I can switch between the tabs and it remains working. When I close one of the two and the other one remains working until both tabs are closed and obviously to browse you need a new tab. > > So, workaround for now is: when I reach a login page, close samsung internet and reopen. Even though this workaround works 100% of the time for me, it has become slightly annoying that I have to keep doing this. Is this a bitwarden or samsung internet app issue? > > Versions > Bitwarden: Version: 2.9.1 (3444) > Samsung Internet: 14.0.1.62 > > Edit: also raised an issue with samsung regarding samsung internet app. So both parties can have a look at it. It seems to be more of an issue with Samsung Internet app than Bitwarden. As if theres a bug how Samsung Internet allows third party apps to use the auto fill feature. Because Bitwarden works fine on other browser apps (chrome, brave and above confirmed by other users: firefox etc) So response from Samsung is as expected utterly useless!! Or the support agent didn't take the time to really read my error description or lack the knowledge to think and see the bigger picture. Their response was: ``` Dear Customer, Thank you for contacting us. We appreciate the opportunity to assist you. I understand you wish to use third party apps. Since we are not directly afilitated we can offer no assistance in this regard. Samsung will not change the browser for a company they have no partnerships with. Also know that you might receive a short survey regarding our interaction. Please take a few seconds to it fill out it would greatly help us improve our customer support experience! ``` I have sent a new inquiry to have them read my problem description again and try to think along. Or is there something you can do without their support @mportune-bw

GiteaMirror commented 2026-05-01 07:56:36 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Apr 19, 2021):

Try contacting them on Twitter @samsunginternet. Their Browser development team is based in the UK, and seems to be pretty separate from the rest of their development, which takes part mostly in India.

<!-- gh-comment-id:822221956 --> @yurividal commented on GitHub (Apr 19, 2021): Try contacting them on Twitter @samsunginternet. Their Browser development team is based in the UK, and seems to be pretty separate from the rest of their development, which takes part mostly in India.

GiteaMirror commented 2026-05-01 07:56:38 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Apr 19, 2021):

Try contacting them on Twitter @SamsungInternet. Their Browser development team is based in the UK, and seems to be pretty separate from the rest of their development, which takes part mostly in India.

I just sent them an email. Hope we get a better response or at least a point into the right direction if they're convinced its not a samsung internet issue.

<!-- gh-comment-id:822231828 --> @Tosko4 commented on GitHub (Apr 19, 2021): > Try contacting them on Twitter @SamsungInternet. Their Browser development team is based in the UK, and seems to be pretty separate from the rest of their development, which takes part mostly in India. I just sent them an email. Hope we get a better response or at least a point into the right direction if they're convinced its not a samsung internet issue.

GiteaMirror commented 2026-05-01 07:56:39 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (Apr 19, 2021):

Samsung will not change the browser for a company they have no partnerships with.

@Tosko4 This is the only substance in the reply. Awhile back we tested the theory that they were whitelisting 3rd party password managers instead of allowing use of the API across the board. I renamed the Bitwarden package name to match another popular password manager that we know works for sure with Samsung Internet, and viola - Bitwarden worked perfectly. We've made several attempts to contact Samsung to add Bitwarden to the whitelist, but we've never received a response.

<!-- gh-comment-id:822674880 --> @mpbw2 commented on GitHub (Apr 19, 2021): > `Samsung will not change the browser for a company they have no partnerships with.` @Tosko4 This is the only substance in the reply. Awhile back we tested the theory that they were whitelisting 3rd party password managers instead of allowing use of the API across the board. I renamed the Bitwarden package name to match another popular password manager that we know works for sure with Samsung Internet, and viola - Bitwarden worked perfectly. We've made several attempts to contact Samsung to add Bitwarden to the whitelist, but we've never received a response.

GiteaMirror commented 2026-05-01 07:56:40 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Apr 19, 2021):

Samsung will not change the browser for a company they have no partnerships with.

@Tosko4 This is the only substance in the reply. Awhile back we tested the theory that they were whitelisting 3rd party password managers instead of allowing use of the API across the board. I renamed the Bitwarden package name to match another popular password manager that we know works for sure with Samsung Internet, and viola - Bitwarden worked perfectly. We've made several attempts to contact Samsung to add Bitwarden to the whitelist, but we've never received a response.

@mportune-bw It's weird. If bitwarden is not whitelisted, then it shouldn't work at all right? Maybe a silly question. But it works for me when I close and reopen samsung internet app. So I tend to lean more towards what @yurividal said, the android autofill api compatibility, no?

<!-- gh-comment-id:822688009 --> @Tosko4 commented on GitHub (Apr 19, 2021): > > `Samsung will not change the browser for a company they have no partnerships with.` > > @Tosko4 This is the only substance in the reply. Awhile back we tested the theory that they were whitelisting 3rd party password managers instead of allowing use of the API across the board. I renamed the Bitwarden package name to match another popular password manager that we know works for sure with Samsung Internet, and viola - Bitwarden worked perfectly. We've made several attempts to contact Samsung to add Bitwarden to the whitelist, but we've never received a response. @mportune-bw It's weird. If bitwarden is not whitelisted, then it shouldn't work at all right? Maybe a silly question. But it works for me when I close and reopen samsung internet app. So I tend to lean more towards what @yurividal said, the android autofill api compatibility, no?

GiteaMirror commented 2026-05-01 07:56:42 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (Apr 19, 2021):

@Tosko4 It's hard to say for sure. The fact that it sometimes works without the whitelist could just be a bug in their whitelist implementation. I can tell you this much though - we don't receive a single blip from the autofill event stream when using Samsung Internet (without the forged package name). It's like it's not even turned on.

<!-- gh-comment-id:822697597 --> @mpbw2 commented on GitHub (Apr 19, 2021): @Tosko4 It's hard to say for sure. The fact that it _sometimes_ works without the whitelist could just be a bug in their whitelist implementation. I can tell you this much though - we don't receive a single blip from the autofill event stream when using Samsung Internet (without the forged package name). It's like it's not even turned on.

GiteaMirror commented 2026-05-01 07:56:43 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Apr 19, 2021):

@mportune-bw gotcha, thanks for responding. I have sent an update to samsung, hoping they respond fingers crossed i'll keep you guys posted

<!-- gh-comment-id:822701370 --> @Tosko4 commented on GitHub (Apr 19, 2021): @mportune-bw gotcha, thanks for responding. I have sent an update to samsung, hoping they respond *fingers crossed* i'll keep you guys posted

GiteaMirror commented 2026-05-01 07:56:45 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Apr 19, 2021):

The "sometimes" working is probably the legacy "Accessibility" api...
We need to make some noise, get our voice heard and hopefully the Samsung Internet team will do something about it...

<!-- gh-comment-id:822701681 --> @yurividal commented on GitHub (Apr 19, 2021): The "sometimes" working is probably the legacy "Accessibility" api... We need to make some noise, get our voice heard and hopefully the Samsung Internet team will do something about it...

GiteaMirror commented 2026-05-01 07:56:46 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (Apr 19, 2021):

@yurividal Fwiw we show a different icon for Accessibility (black & white shield, vs blue for Autofill) for exactly this purpose. It was becoming nearly impossible to troubleshoot when users had both enabled and they were visually identical.

<!-- gh-comment-id:822723076 --> @mpbw2 commented on GitHub (Apr 19, 2021): @yurividal Fwiw we show a different icon for Accessibility (black & white shield, vs blue for Autofill) for exactly this purpose. It was becoming nearly impossible to troubleshoot when users had both enabled and they were visually identical.

GiteaMirror commented 2026-05-01 07:56:47 -05:00

Author

Owner

Copy Link

@Phangan commented on GitHub (Apr 20, 2021):

Could you give us a "beta" version that has a forged package name until Samsung has finally fixed this?

<!-- gh-comment-id:823492009 --> @Phangan commented on GitHub (Apr 20, 2021): Could you give us a "beta" version that has a forged package name until Samsung has finally fixed this?

GiteaMirror commented 2026-05-01 07:56:49 -05:00

Author

Owner

Copy Link

@ghost commented on GitHub (Apr 20, 2021):

You'd think Samsung would want to gain market share for their mobile browser. 🤔

<!-- gh-comment-id:823499550 --> @ghost commented on GitHub (Apr 20, 2021): You'd think Samsung would want to gain market share for their mobile browser. 🤔

GiteaMirror commented 2026-05-01 07:56:50 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (Apr 20, 2021):

Could you give us a "beta" version that has a forged package name until Samsung has finally fixed this?

That would be a bad idea for lots of reasons that are beyond the scope of this issue. :)

<!-- gh-comment-id:823521116 --> @mpbw2 commented on GitHub (Apr 20, 2021): > Could you give us a "beta" version that has a forged package name until Samsung has finally fixed this? That would be a bad idea for lots of reasons that are beyond the scope of this issue. :)

GiteaMirror commented 2026-05-01 07:56:58 -05:00

Author

Owner

Copy Link

@ghost commented on GitHub (Apr 20, 2021):

Is there anything that we can do to help get their attention? Is there no way to get in contact with an engineer that maintains the Samsung Browser?

Surely there is some channel for communication, or someone with contacts within Samsung?

From what I understand it works fine with other password managers.

Would a smaller company like AgileBits be willing to provide insight on this issue? I know they're Bitwarden's competition, but it would be nice for someone to help for the "greater good" of providing a safe and secure web.

<!-- gh-comment-id:823525706 --> @ghost commented on GitHub (Apr 20, 2021): Is there anything that we can do to help get their attention? Is there no way to get in contact with an engineer that maintains the Samsung Browser? Surely there is some channel for communication, or someone with contacts within Samsung? From what I understand it works fine with other password managers. Would a smaller company like AgileBits be willing to provide insight on this issue? I know they're Bitwarden's competition, but it would be nice for someone to help for the "greater good" of providing a safe and secure web.

GiteaMirror commented 2026-05-01 07:56:59 -05:00

Author

Owner

Copy Link

@Phangan commented on GitHub (Apr 20, 2021):

@mportune-bw Sorry, I forgot to add some irony, don't take this too seriously! ;)

<!-- gh-comment-id:823540762 --> @Phangan commented on GitHub (Apr 20, 2021): @mportune-bw Sorry, I forgot to add some irony, don't take this too seriously! ;)

GiteaMirror commented 2026-05-01 07:57:01 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (Apr 20, 2021):

@Phangan Understood, lol :)

So I just updated to Samsung Internet 14 stable, and Autofill is working and even supports inline via the Samsung keyboard. Both of these things are something I never expected to see. Anybody else? (I'm on an S10 w/ Android 11)

<!-- gh-comment-id:823563794 --> @mpbw2 commented on GitHub (Apr 20, 2021): @Phangan Understood, lol :) So I just updated to Samsung Internet 14 stable, and Autofill is working and even supports inline via the Samsung keyboard. Both of these things are something I never expected to see. Anybody else? (I'm on an S10 w/ Android 11)

GiteaMirror commented 2026-05-01 07:57:02 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Apr 20, 2021):

@mportune-bw as you can see in the version numbering here: https://github.com/bitwarden/mobile/issues/895#issuecomment-822058758

I've been rocking 14 stable but experience the bug. So annoying. The dev has it all working and users have issues xD

<!-- gh-comment-id:823568474 --> @Tosko4 commented on GitHub (Apr 20, 2021): @mportune-bw as you can see in the version numbering here: https://github.com/bitwarden/mobile/issues/895#issuecomment-822058758 I've been rocking 14 stable but experience the bug. So annoying. The dev has it all working and users have issues xD

GiteaMirror commented 2026-05-01 07:57:03 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (Apr 20, 2021):

@Tosko4 Bummer, mine is the same browser build. The only difference is I'm running an internal build of Bitwarden (2.9.2) but I don't believe anything autofill related has been touched since 2.9.1. Hopefully I can get a beta out relatively soon in case i'm wrong.

<!-- gh-comment-id:823572469 --> @mpbw2 commented on GitHub (Apr 20, 2021): @Tosko4 Bummer, mine is the same browser build. The only difference is I'm running an internal build of Bitwarden (2.9.2) but I don't believe anything autofill related has been touched since 2.9.1. Hopefully I can get a beta out relatively soon in case i'm wrong.

GiteaMirror commented 2026-05-01 07:57:05 -05:00

Author

Owner

Copy Link

@ghost commented on GitHub (Apr 20, 2021):

So I just updated to Samsung Internet 14 stable, and Autofill is working and even supports inline via the Samsung keyboard. Both of these things are something I never expected to see. Anybody else? (I'm on an S10 w/ Android 11)

It doesn't work for me at all. Only the accessibility service works for me.

Samsung Internet v14.0.1.62
Samsung Galaxy S21 Ultra (Android 11)
Samsung Keyboard v5.2.40.0

<!-- gh-comment-id:823577124 --> @ghost commented on GitHub (Apr 20, 2021): > So I just updated to Samsung Internet 14 stable, and Autofill is working and even supports inline via the Samsung keyboard. Both of these things are something I never expected to see. Anybody else? (I'm on an S10 w/ Android 11) It doesn't work for me at all. Only the accessibility service works for me. Samsung Internet v14.0.1.62 Samsung Galaxy S21 Ultra (Android 11) Samsung Keyboard v5.2.40.0

GiteaMirror commented 2026-05-01 07:57:06 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (Apr 20, 2021):

Just confirming - has everyone disabled the browser's built-in autofill settings in Internet Settings > Personal Data > Autofill forms (and the two switches in Usernames and passwords)?

<!-- gh-comment-id:823583038 --> @mpbw2 commented on GitHub (Apr 20, 2021): Just confirming - has everyone disabled the browser's built-in autofill settings in **Internet Settings > Personal Data > Autofill forms** (and the two switches in **Usernames and passwords**)?

GiteaMirror commented 2026-05-01 07:57:07 -05:00

Author

Owner

Copy Link

@ghost commented on GitHub (Apr 20, 2021):

Just confirming - has everyone disabled the browser's built-in autofill settings in Internet Settings > Personal Data > Autofill forms (and the two switches in Usernames and passwords)?

Yes, I disabled all of those settings a long time ago and I just confirmed that they are still disabled.

Thanks again for trying to help.

Samsung DeX mode on their latest tablets is really awesome and the DeX experience in the browser is also great.

I just can't bring myself to use the browser without proper support for Bitwarden.

<!-- gh-comment-id:823585277 --> @ghost commented on GitHub (Apr 20, 2021): > Just confirming - has everyone disabled the browser's built-in autofill settings in **Internet Settings > Personal Data > Autofill forms** (and the two switches in **Usernames and passwords**)? > Yes, I disabled all of those settings a long time ago and I just confirmed that they are still disabled. Thanks again for trying to help. Samsung DeX mode on their latest tablets is really awesome and the DeX experience in the browser is also great. I just can't bring myself to use the browser without proper support for Bitwarden.

GiteaMirror commented 2026-05-01 07:57:09 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Apr 20, 2021):

Just confirming - has everyone disabled the browser's built-in autofill settings in Internet Settings > Personal Data > Autofill forms (and the two switches in Usernames and passwords)?

Yep. All disabled

<!-- gh-comment-id:823596183 --> @Tosko4 commented on GitHub (Apr 20, 2021): > Just confirming - has everyone disabled the browser's built-in autofill settings in **Internet Settings > Personal Data > Autofill forms** (and the two switches in **Usernames and passwords**)? Yep. All disabled

GiteaMirror commented 2026-05-01 07:57:10 -05:00

Author

Owner

Copy Link

@raghusundaram commented on GitHub (Apr 21, 2021):

@mportune-bw i found out when it stops working and what to do as a workaround to make it work again. When I go to the tab view in Samsung internet and open a new tab, i go to the login page of that particular website, and bitwarden doesn't work. When I close the samsung internet app and re-open it. It starts loading the login page of that particular website again and voila, bitwarden works.

Test scenario 2: when i open two new tabs with two different websited and go to the login pages of both websites, close samsung internet and reopen the app, then bitwarden works on both tabs. I can switch between the tabs and it remains working. When I close one of the two and the other one remains working until both tabs are closed and obviously to browse you need a new tab.

So, workaround for now is: when I reach a login page, close samsung internet and reopen. Even though this workaround works 100% of the time for me, it has become slightly annoying that I have to keep doing this. Is this a bitwarden or samsung internet app issue?

Versions
Bitwarden: Version: 2.9.1 (3444)
Samsung Internet: 14.0.1.62

Edit: also raised an issue with samsung regarding samsung internet app. So both parties can have a look at it. It seems to be more of an issue with Samsung Internet app than Bitwarden. As if theres a bug how Samsung Internet allows third party apps to use the auto fill feature. Because Bitwarden works fine on other browser apps (chrome, brave and above confirmed by other users: firefox etc)

The above solution works here.
Bitwarden working natively.

<!-- gh-comment-id:823831576 --> @raghusundaram commented on GitHub (Apr 21, 2021): > @mportune-bw i found out when it stops working and what to do as a workaround to make it work again. When I go to the tab view in Samsung internet and open a new tab, i go to the login page of that particular website, and bitwarden doesn't work. When I close the samsung internet app and re-open it. It starts loading the login page of that particular website again and voila, bitwarden works. > > Test scenario 2: when i open two new tabs with two different websited and go to the login pages of both websites, close samsung internet and reopen the app, then bitwarden works on both tabs. I can switch between the tabs and it remains working. When I close one of the two and the other one remains working until both tabs are closed and obviously to browse you need a new tab. > > So, workaround for now is: when I reach a login page, close samsung internet and reopen. Even though this workaround works 100% of the time for me, it has become slightly annoying that I have to keep doing this. Is this a bitwarden or samsung internet app issue? > > Versions > Bitwarden: Version: 2.9.1 (3444) > Samsung Internet: 14.0.1.62 > > Edit: also raised an issue with samsung regarding samsung internet app. So both parties can have a look at it. It seems to be more of an issue with Samsung Internet app than Bitwarden. As if theres a bug how Samsung Internet allows third party apps to use the auto fill feature. Because Bitwarden works fine on other browser apps (chrome, brave and above confirmed by other users: firefox etc) The above solution works here. Bitwarden working natively.

GiteaMirror commented 2026-05-01 07:57:13 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Apr 21, 2021):

@Tosko4 Bummer, mine is the same browser build. The only difference is I'm running an internal build of Bitwarden (2.9.2) but I don't believe anything autofill related has been touched since 2.9.1. Hopefully I can get a beta out relatively soon in case i'm wrong.

Same build here. In-line autofill does "work", but, as stated before, it only works sometimes. In many occasions bitwarden does not recognize the website (it either identifies the website as being "--" or being "com.sec.android.app.sbrowser.beta") so you have to manually search for the site in bitwarden. Then, clicking the correct site, it also only actually fills in sometimes.

<!-- gh-comment-id:823851087 --> @yurividal commented on GitHub (Apr 21, 2021): > @Tosko4 Bummer, mine is the same browser build. The only difference is I'm running an internal build of Bitwarden (2.9.2) but I don't believe anything autofill related has been touched since 2.9.1. Hopefully I can get a beta out relatively soon in case i'm wrong. Same build here. In-line autofill does "work", but, as stated before, it only works sometimes. In many occasions bitwarden does not recognize the website (it either identifies the website as being "--" or being "com.sec.android.app.sbrowser.beta") so you have to manually search for the site in bitwarden. Then, clicking the correct site, it also only actually fills in sometimes.

GiteaMirror commented 2026-05-01 07:57:14 -05:00

Author

Owner

Copy Link

@mdvmeijer commented on GitHub (Aug 23, 2021):

@Tosko4 This is the only substance in the reply. Awhile back we tested the theory that they were whitelisting 3rd party password managers instead of allowing use of the API across the board. I renamed the Bitwarden package name to match another popular password manager that we know works for sure with Samsung Internet, and viola - Bitwarden worked perfectly. We've made several attempts to contact Samsung to add Bitwarden to the whitelist, but we've never received a response.

From what I can see of the curent behaviour of the Bitwarden app, it seems to have been added to this 'whitelist'. Would you mind sharing how you managed to fix this in the end? I am running into the same issue with my own project.

<!-- gh-comment-id:903579087 --> @mdvmeijer commented on GitHub (Aug 23, 2021): > @Tosko4 This is the only substance in the reply. Awhile back we tested the theory that they were whitelisting 3rd party password managers instead of allowing use of the API across the board. I renamed the Bitwarden package name to match another popular password manager that we know works for sure with Samsung Internet, and viola - Bitwarden worked perfectly. We've made several attempts to contact Samsung to add Bitwarden to the whitelist, but we've never received a response. From what I can see of the curent behaviour of the Bitwarden app, it seems to have been added to this 'whitelist'. Would you mind sharing how you managed to fix this in the end? I am running into the same issue with my own project.

GiteaMirror commented 2026-05-01 07:57:16 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Aug 23, 2021):

The weirdest thing is that, if you close Samsung browser (recents, swipe up) and relaunch it, bitwarden works and you get the inline autofill. It works for a while, and then after some minutes it stops again. So, it's definitely some sort of timer or timeout that is going on, that somehow kills the autofill service for the browser.

<!-- gh-comment-id:903583843 --> @yurividal commented on GitHub (Aug 23, 2021): The weirdest thing is that, if you close Samsung browser (recents, swipe up) and relaunch it, bitwarden works and you get the inline autofill. It works for a while, and then after some minutes it stops again. So, it's definitely some sort of timer or timeout that is going on, that somehow kills the autofill service for the browser.

GiteaMirror commented 2026-05-01 07:57:17 -05:00

Author

Owner

Copy Link

@mdvmeijer commented on GitHub (Aug 31, 2021):

@yurividal So if I understand correctly, you still have problems with the Bitwarden autofill service in combination with the Samsung browser? I did some tests today of both the accessibility service and the autofill service with the browser, and they functioned as they should for at least 15 minutes (as long as I ran the tests) so the problem seems fixed on my end (most recent versions of Bitwarden and the Samsung browser)

<!-- gh-comment-id:909243733 --> @mdvmeijer commented on GitHub (Aug 31, 2021): @yurividal So if I understand correctly, you still have problems with the Bitwarden autofill service in combination with the Samsung browser? I did some tests today of both the accessibility service and the autofill service with the browser, and they functioned as they should for at least 15 minutes (as long as I ran the tests) so the problem seems fixed on my end (most recent versions of Bitwarden and the Samsung browser)

GiteaMirror commented 2026-05-01 07:57:19 -05:00

Author

Owner

Copy Link

@ghost commented on GitHub (Aug 31, 2021):

@yurividal So if I understand correctly, you still have problems with the Bitwarden autofill service in combination with the Samsung browser? I did some tests today of both the accessibility service and the autofill service with the browser, and they functioned as they should for at least 15 minutes (as long as I ran the tests) so the problem seems fixed on my end (most recent versions of Bitwarden and the Samsung browser)

@mdvmeijer Only the accessibility service prompt pops up, and once in a while even that fails.

Samsung Galaxy S21 Ultra running Android 11 w/ One UI 3.1

<!-- gh-comment-id:909255120 --> @ghost commented on GitHub (Aug 31, 2021): > @yurividal So if I understand correctly, you still have problems with the Bitwarden autofill service in combination with the Samsung browser? I did some tests today of both the accessibility service and the autofill service with the browser, and they functioned as they should for at least 15 minutes (as long as I ran the tests) so the problem seems fixed on my end (most recent versions of Bitwarden and the Samsung browser) > > @mdvmeijer Only the accessibility service prompt pops up, and once in a while even that fails. Samsung Galaxy S21 Ultra running Android 11 w/ One UI 3.1

GiteaMirror commented 2026-05-01 07:57:22 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Aug 31, 2021):

@yurividal So if I understand correctly, you still have problems with the Bitwarden autofill service in combination with the Samsung browser? I did some tests today of both the accessibility service and the autofill service with the browser, and they functioned as they should for at least 15 minutes (as long as I ran the tests) so the problem seems fixed on my end (most recent versions of Bitwarden and the Samsung browser)

Accessibility is completely disabled, to make sure I'm using autofill API. Autofill works with Samsung Browser only sometimes. It's like if the service has some sort of timeout. If you kill the browser (swipe up from recent) and relaunch the browser on the same page, autofill will work.
After some minutes, it stops again. This only happens on the browser. For other autofill areas, such as apps, it works pretty consistently.

<!-- gh-comment-id:909341991 --> @yurividal commented on GitHub (Aug 31, 2021): > @yurividal So if I understand correctly, you still have problems with the Bitwarden autofill service in combination with the Samsung browser? I did some tests today of both the accessibility service and the autofill service with the browser, and they functioned as they should for at least 15 minutes (as long as I ran the tests) so the problem seems fixed on my end (most recent versions of Bitwarden and the Samsung browser) Accessibility is completely disabled, to make sure I'm using autofill API. Autofill works with Samsung Browser only sometimes. It's like if the service has some sort of timeout. If you kill the browser (swipe up from recent) and relaunch the browser on the same page, autofill will work. After some minutes, it stops again. This only happens on the browser. For other autofill areas, such as apps, it works pretty consistently.

GiteaMirror commented 2026-05-01 07:57:25 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Aug 31, 2021):

It can also be related to turning the screen off, instead of an actual timeout.

<!-- gh-comment-id:909342852 --> @yurividal commented on GitHub (Aug 31, 2021): It can also be related to turning the screen off, instead of an actual timeout.

GiteaMirror commented 2026-05-01 07:57:30 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Aug 31, 2021):

@mdvmeijer this video shows exactly what I mean:

<!-- gh-comment-id:909480631 --> @yurividal commented on GitHub (Aug 31, 2021): @mdvmeijer this video shows exactly what I mean: 

GiteaMirror commented 2026-05-01 07:57:32 -05:00

Author

Owner

Copy Link

@mdvmeijer commented on GitHub (Sep 1, 2021):

I see, it indeed seems like there is still something interfering with the autofill service.
Regarding the accessibility service and why I think Bitwarden managed to get into this "Samsung whitelist": When I just have the accessibility service of my own app running, no accessibility events are emitted by the app. Hence it can provide no functionality at all to the user if they are using the Samsung browser. However, if I enable the accessibility (or autofill, works for both) service of Bitwarden, the Samsung browser starts emitting accessibility events. These can then also be caught by my app. However, if I disable the Bitwarden service the browser stops emitting events again. Hence it looks like the Samsung browser notices whether Bitwarden is running, and based on that either emits these accessibility events or not. The same is the case with Dashlane and Lastpass: if either of them run, the browser emits events.

@mportune-bw Could you maybe shed some light on this or is this still a mystery to the team?

<!-- gh-comment-id:910128046 --> @mdvmeijer commented on GitHub (Sep 1, 2021): I see, it indeed seems like there is still something interfering with the autofill service. Regarding the accessibility service and why I think Bitwarden managed to get into this "Samsung whitelist": When I just have the accessibility service of my own app running, no accessibility events are emitted by the app. Hence it can provide no functionality at all to the user if they are using the Samsung browser. However, if I enable the accessibility (or autofill, works for both) service of Bitwarden, the Samsung browser starts emitting accessibility events. These can then also be caught by my app. However, if I disable the Bitwarden service the browser stops emitting events again. Hence it looks like the Samsung browser notices whether Bitwarden is running, and based on that either emits these accessibility events or not. The same is the case with Dashlane and Lastpass: if either of them run, the browser emits events. @mportune-bw Could you maybe shed some light on this or is this still a mystery to the team?

GiteaMirror commented 2026-05-01 07:57:34 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Sep 1, 2021):

I have the same issue as @yurividal , i mentioned this before in a previous comment. But I'd like to point out something. Might help troubleshooting, because we might be looking in the wrong area. It's not just Samsung Browser related. Other browsers have same issue with bitwarden, exactly the same as recorded in @yurividal his video. Such as, chrome, brave etc. Sometimes bitwarden recognizes the login field and shows the bitwarden button to fill in credentials. Other times it doesn't, I close the browser, reopen the browser and voila, bitwarden button is shown.

I believe the issue is not a compatibility problem with a specific browser, or a whitelisting issue, but more fundamental.

On my iOS devices I don't have issues with bitwarden, only on Android devices.

@MattTheDev
@mportune-bw

<!-- gh-comment-id:910140442 --> @Tosko4 commented on GitHub (Sep 1, 2021): I have the same issue as @yurividal , i mentioned this before in a previous comment. But I'd like to point out something. Might help troubleshooting, because we might be looking in the wrong area. It's not just Samsung Browser related. Other browsers have same issue with bitwarden, exactly the same as recorded in @yurividal his video. Such as, chrome, brave etc. Sometimes bitwarden recognizes the login field and shows the bitwarden button to fill in credentials. Other times it doesn't, I close the browser, reopen the browser and voila, bitwarden button is shown. I believe the issue is not a compatibility problem with a specific browser, or a whitelisting issue, but more fundamental. On my iOS devices I don't have issues with bitwarden, only on Android devices. @MattTheDev @mportune-bw

GiteaMirror commented 2026-05-01 07:57:35 -05:00

Author

Owner

Copy Link

@mdvmeijer commented on GitHub (Sep 1, 2021):

@Tosko4 True, this sounds like a more fundamental problem separate from the whitelisting stuff. I can confirm from my own testing that this whitelist does exist however, and somehow Bitwarden managed to get on it (maybe someone at the Samsung browser dev team really likes Bitwarden :p). If someone on the Bitwarden team has any idea how you managed this then I'd love to hear it.

<!-- gh-comment-id:910150991 --> @mdvmeijer commented on GitHub (Sep 1, 2021): @Tosko4 True, this sounds like a more fundamental problem separate from the whitelisting stuff. I can confirm from my own testing that this whitelist does exist however, and somehow Bitwarden managed to get on it (maybe someone at the Samsung browser dev team really likes Bitwarden :p). If someone on the Bitwarden team has any idea how you managed this then I'd love to hear it.

GiteaMirror commented 2026-05-01 07:57:37 -05:00

Author

Owner

Copy Link

@mpbw2 commented on GitHub (Sep 1, 2021):

@mdvmeijer Based on the power consumption used by accessibility (the event stream can be insane depending on the app) I would guess they stop emitting events unless an app is configured to receive them. I don't know this for sure, however.

@Tosko4 I would love to know the answer to this as well, since debugging shows our autofill service alive and well but simply no longer receiving events from the system.

@mdvmeijer We've tried to contact them in the past to get whitelisted but never heard anything back. Maybe they finally added us.

<!-- gh-comment-id:910293046 --> @mpbw2 commented on GitHub (Sep 1, 2021): @mdvmeijer Based on the power consumption used by accessibility (the event stream can be insane depending on the app) I would guess they stop emitting events unless an app is configured to receive them. I don't know this for sure, however. @Tosko4 I would love to know the answer to this as well, since debugging shows our autofill service alive and well but simply no longer receiving events from the system. @mdvmeijer We've tried to contact them in the past to get whitelisted but never heard anything back. Maybe they finally added us.

GiteaMirror commented 2026-05-01 07:57:39 -05:00

Author

Owner

Copy Link

@Tosko4 commented on GitHub (Sep 1, 2021):

@mportune-bw I tried putting the apps related to each other (Brave, Bitwarden, Chrome, Samsung Browser) in a never deep sleep mode.

The new power management on android creates a lot of issues so to say. Not sure if you were referring to that? I'd have no clue how I could help any further honestly. If theres anything I can provide, let me know

<!-- gh-comment-id:910360751 --> @Tosko4 commented on GitHub (Sep 1, 2021): @mportune-bw I tried putting the apps related to each other (Brave, Bitwarden, Chrome, Samsung Browser) in a never deep sleep mode. The new power management on android creates a lot of issues so to say. Not sure if you were referring to that? I'd have no clue how I could help any further honestly. If theres anything I can provide, let me know

GiteaMirror commented 2026-05-01 07:57:42 -05:00

Author

Owner

Copy Link

@ghost commented on GitHub (Sep 1, 2021):

@mportune-bw I tried putting the apps related to each other (Brave, Bitwarden, Chrome, Samsung Browser) in a never deep sleep mode.

The new power management on android creates a lot of issues so to say. Not sure if you were referring to that? I'd have no clue how I could help any further honestly. If theres anything I can provide, let me know

I've excluded these apps from deep sleep as well and still have more issues with Samsung Internet than other Chromium based browser.

Honestly, why is autofill such a nightmare in Android? It's been a buggy mess for so long now.

<!-- gh-comment-id:910366759 --> @ghost commented on GitHub (Sep 1, 2021): > @mportune-bw I tried putting the apps related to each other (Brave, Bitwarden, Chrome, Samsung Browser) in a never deep sleep mode. > > The new power management on android creates a lot of issues so to say. Not sure if you were referring to that? I'd have no clue how I could help any further honestly. If theres anything I can provide, let me know I've excluded these apps from deep sleep as well and still have more issues with Samsung Internet than other Chromium based browser. Honestly, why is autofill such a nightmare in Android? It's been a buggy mess for so long now.

GiteaMirror commented 2026-05-01 07:57:44 -05:00

Author

Owner

Copy Link

@yurividal commented on GitHub (Sep 1, 2021):

@douglasparker i think the reason why its a mess is because it depends on a proper and precise implementation from Browsers, Keyboards, and Password Providers. 3 different players have to work together to have it work properly. No wonder why the only proper implementation is on pixel phones using Chrome, GBoard and Google Password Manager.

<!-- gh-comment-id:910379148 --> @yurividal commented on GitHub (Sep 1, 2021): @douglasparker i think the reason why its a mess is because it depends on a proper and precise implementation from Browsers, Keyboards, and Password Providers. 3 different players have to work together to have it work properly. No wonder why the only proper implementation is on pixel phones using Chrome, GBoard and Google Password Manager.

GiteaMirror commented 2026-05-01 07:57:45 -05:00

Author

Owner

Copy Link

@mdvmeijer commented on GitHub (Sep 7, 2021):

@mdvmeijer We've tried to contact them in the past to get whitelisted but never heard anything back. Maybe they finally added us.

@mportune-bw Thank you for your reply. Do you know which channel was used to try to contact them? Then I will try my luck as well.

<!-- gh-comment-id:914070464 --> @mdvmeijer commented on GitHub (Sep 7, 2021): > @mdvmeijer We've tried to contact them in the past to get whitelisted but never heard anything back. Maybe they finally added us. @mportune-bw Thank you for your reply. Do you know which channel was used to try to contact them? Then I will try my luck as well.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

sdlc/sdk-update

new-item-types/PM-32810_bank-account-view

new-item-types/PM-32810_bank-account

beta-for-qa

BWA-253/not-displaying-totp-coded-with-empty-key

target-sdk-37

vvolkgang/renovate-remove-group

pm-34038/card-scanner-qa-fixes

PM-33982/build-device-screen

PM-30625/filter-out-empty-totp-vault-count

vvolkgang/update-jira-release-notes

new-item-types/PM-34123_new-item-menu

new-item-types/PM-32806_passport

new-item-types/PM-32808_drivers-license

BWA-99/show-next-totp

BWA-99/add-preview-next-totp-code-setting

renovate/glidecompose

chore/improve-android-ui-verification-skill

sync-min-sdk

release/2026.4-rc51

fix/security-sast-22741894-bvwj

related-origin-passkey-creation

release/2026.4-rc50

platform/android-breaking-change-detection

innovation-sprint-2026-send-folder

release/2026.3-rc49

PM-34193-vault-lockout

android-collections

llm/add-resolving-sdk-updates-skill

QA-1523/sanity-test-saucelabs

release/2026.3-rc48

PM-26577-app-links-support

PM-26896-autofill-fix

release/2026.2-rc47

pr-6572

release/2026.2-rc46

release/2026.1-rc45

PM-30644/added-logs-for-debug

PM-30644/quicktile-nav-not-showing-migration

minor-gradle-updates

release/2026.1-rc42

release/2026.1-rc44

release/2026.1-rc43

PM-28834/set-landscape-on-horizonos-devices

PM-28468/validate-and-navigate-to-vault-migration

PM-20026/force-ltr-passwords-and-codes

release/2025.12-rc41

cmcg/testCoverage

PM-29014/talkback-support-for-passwords

release/2025.12-rc40

BRE-1305/publish_test

accept-user-certs

autofill-permissions

release/2025.11-rc39

PM-22479/check-all-certificates-validate-asset-links

release/2025.10-rc38

agalles/android-latest

retro-agent

PM-27001/skip-account-selection-only-one-exists-cxp

release/2025.10-rc37

agalles/test-1118

release/2025.10-rc36

PM-20593-token-refresh

QA-1126b/adding-native-sanity-test

release/2025.9-rc35

pm-25933/sdk-update-password

release/2025.9-rc34

release/2025.8-rc33

agalles/20250821-release

debug-release-issues

pm-24249-allow-automated-prs-for-sdk-updates

release/2025.8-rc32

release/WORKFLOW-TEST-2025.8-rc28

agalles/20250807release

release/2025.07-rc25

release/hotfix-v2025.7.0-bwa

pm-23311/export-vault-policy-bypass

release/2025.07-rc24

authenticator-pm-sync-flags-issue

release/hotfix-v2025.6.0-bwpm

release/2025.06-rc21

agalles/automate-android-fastlane-patch

release/2025.05-rc20

release/2025.04-rc19

languages/basque

release/2025.03-rc19

update-readme

qrcode/feature

innovation/archive/pm-19153-archive-items

qrcode/2-ui-fields

qrcode/1-page

hold-on-biometric-prompt-alternative

release-notes-process

release/2025.02-rc16

bwa-monorepo

PM-8223/new-device-verification-ux-improvements

pm-18451/exempt-from-policies

test-bwa

release/2025.01-rc15

release/2025.01-rc14

release/2024.12-rc13

pm-16670/sync-leave-notice

821

PM-16695/backport-lean-more-new-device-verification

release/hotfix-v2024.11.7

release/2024.11-rc1

pm-11304/collection-add-item-button

PM-14241/disabling-logs-app-crash

poc/offline-editing

new-version-calc

pm-11649/expired-link-services

pm-6702/add-feature-flag

pm-6702/email-verification-feature

pm-9933/marketing-copy-update

pm-6702/registration-flows

update-templates

pm-6701/email-verification-selfhost-registration

v2026.4.0-bwa

v2026.4.0-bwpm

v2026.3.1-bwa

v2026.3.1-bwpm

v2026.3.0-bwpm

v2026.3.0-bwa

v2026.2.1-bwpm

v2026.2.1-bwa

v2026.2.0-bwpm

v2026.2.0-bwa

v2026.1.1-bwa

v2026.1.1-bwpm

temp-test

v2026.1.0-bwpm

v2026.1.0-bwa

v2025.12.1-bwa

v2025.12.1-bwpm

v2025.12.0-bwa

v2025.12.0-bwpm

v2025.11.1-bwpm

v2025.11.1-bwa

v2025.11.0-bwpm

v2025.11.0-bwa

v2025.10.1-bwa

v2025.10.1-bwpm

v2025.10.0-bwa

v2025.10.0-bwpm

v2025.9.1-bwa

v2025.9.1-bwpm

v2025.9.0-bwa

v2025.9.0-bwpm

v2025.8.1-bwa

v2025.8.1-bwpm

v2025.8.0-bwa

v2025.8.0-bwpm

v2025.7.2-bwa

v2025.7.2-bwpm

v2025.7.1-bwa

v2025.7.1-bwpm

v2025.7.0-bwa

v2025.7.0-bwpm

v2025.6.1-bwpm

v2025.6.0-bwa

v2025.6.0-bwpm

v2025.1.0-bwa

v2025.5.0-bwa

v2025.5.0-bwpm

v2025.5.999

2025.4.0

v2025.4.0

untagged-4731eaadac73f3dfbbb8

v2025.3.0

v2025.2.0

untagged-815a165c5d70ffe75bc7

v2025.1.2

v2025.1.1

v2025.1.0

v2024.12.0

untagged-5a76b6392a4c8998c63a

v2024.11.7

v2024.11.6

v2024.11.5

v2024.11.4

v2024.11.3

v2024.11.2

v2024.11.1

v2024.11.0

v2024.10.2

v2024.10.1

v2024.10.0

v2024.9.0

v2024.8.1

v2024.8.0

v2024.7.3

v2024.7.2

v2024.7.1

v2024.7.0

v2024.6.1

v2024.6.0

v2024.5.1

v2024.4.1

v2024.4.2

v2024.4.0

v2024.3.3

v2024.3.1

v2024.3.0

v2024.2.1

v2024.2.0

v2024.1.1

v2024.1.0

v2023.12.0

v2023.10.0

v2023.9.2

maui-single-project-android

v2023.9.1

v2023.9.0

v2023.8.0

v2023.7.0

v2023.5.0

v2023.4.0

v2023.3.2

v2023.3.1

v2023.3.0

v2023.2.0

v2023.1.0

v2022.11.0

v2022.10.0

v2022.9.1

v2022.9.0

v2022.8.0

v2022.6.2

v2022.6.1

v2022.6.0

v2022.05.0

v2.18.0

v2.17.0

v2.16.4

v2.16.3

v2.16.2

v2.16.1

v2.15.0

v2.14.2

v2.14.1

v2.14.0

v2.13.0

v2.12.0

v2.11.3

v2.11.2

v2.11.1

v2.11.0

v2.10.0

v2.9.1

v2.9.0

v2.8.2

v2.8.1

v2.8.0

v2.7.2

v2.7.0

v2.6.1

v2.6.0

v2.5.6

v.2.5.5

v2.5.5

v2.5.4

v2.5.3

v2.5.2

v2.5.1

v2.5.0

v2.4.3

v2.4.2

v2.4.1

v2.4.0

v2.3.1

v2.3.0

v2.2.8

v2.2.7

v2.2.6

v2.2.2

v2.2.1

v2.2.0

v2.1.2

v2.1.0

v2.0.6

v2.0.5

v2.0.4

v2.0.3

v2.0.2

v2.0.1

v2.0.0

v1.22.1

v1.22.0

v1.21.0

v1.20.0

v1.19.0

v1.18.1

v1.18.0

v1.17.0

v1.16.0

v1.15.2

v1.15.1

v1.15.0

v1.14.4

v1.14.1

v1.14.0

v1.13.0

v1.12.2

v1.12.1

v1.12.0

v1.11.1

v1.11.0

v1.10.0

v1.9.0

v1.8.1

v1.8.0

v1.7.0

v1.6.5

v1.6.1

v1.6.0

v1.5.1

v1.5.0

v1.4.4

v1.4.3

v1.4.0

v1.3.0

v1.2.1

v1.2.0

v1.1.0

v1.0.0

v0.0.6

v0.0.5

v0.0.4

v0.0.3

v0.0.2

v0.0.1

Labels

Clear labels

app:authenticator

app:password-manager

bug

bug-passkey

customer-support

duplicate

enhancement

good first issue

help wanted

needs-reply

needs-response

pull-request

Mirrored from GitHub Pull Request

question

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/android#49091