[GH-ISSUE #5080] Autofill missing in Ecosia browser #88645

Open
opened 2026-05-26 23:15:27 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @gprezza on GitHub (Apr 19, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5080

Steps To Reproduce

Fill any password field in Ecosia browser

Expected Result

Bitwarden autofill should pop up

Actual Result

No Bitwarden autofill pops up

Screenshots or Videos

No response

Additional Context

This is similar to #344 The issue doesn't seem to be solved since no Bitwarden autofill is prompted in any password field.

Build Version

2025.3.0 (19983)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Android 14
Ecosia Browser 12.1.2.720 (12.1.2)
Samsung Galaxy S21 5G

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @gprezza on GitHub (Apr 19, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5080 ### Steps To Reproduce Fill any password field in Ecosia browser ### Expected Result Bitwarden autofill should pop up ### Actual Result No Bitwarden autofill pops up ### Screenshots or Videos _No response_ ### Additional Context This is similar to [#344](https://github.com/bitwarden/mobile/issues/344) The issue doesn't seem to be solved since no Bitwarden autofill is prompted in any password field. ### Build Version 2025.3.0 (19983) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Android 14 Ecosia Browser 12.1.2.720 (12.1.2) Samsung Galaxy S21 5G ### Issue Tracking Info - [ ] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bugapp:password-manager labels 2026-05-26 23:15:28 -05:00
Author
Owner

@S-Kakar commented on GitHub (Apr 19, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-20435

<!-- gh-comment-id:2816570956 --> @S-Kakar commented on GitHub (Apr 19, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-20435
Author
Owner

@cbw23 commented on GitHub (Apr 20, 2025):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

<!-- gh-comment-id:2817266106 --> @cbw23 commented on GitHub (Apr 20, 2025): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
Author
Owner

@emmgfx commented on GitHub (Aug 20, 2025):

Any news about this? Isn't working for me. Passkeys aren't working, also

<!-- gh-comment-id:3207335834 --> @emmgfx commented on GitHub (Aug 20, 2025): Any news about this? Isn't working for me. Passkeys aren't working, also
Author
Owner

@SaintPatrck commented on GitHub (Aug 20, 2025):

Hi all,

Ecosia appears to be a Chromium browser. Chrome, and subsequently all Chromium based browsers, recently changed autofill settings such that 3rd party credential managers MUST be given explicit permission to perform autofill. More details about the change can be found in Google's Chrome on Android to support third-party autofill services natively blog post. We have also updated our help article on Android Browser Integration. Although Chrome and Brave are the only browsers we mention by name, the same applies to all Chromium based browsers.

That being said, I did a quick check and can confirm that the latest version of Ecosia (12.1.3) is not sending autofill requests to Bitwarden. I also searched through Ecosia's settings and I'm unable to locate the Autofill settings that are necessary to enable "Autofill using another service" as described in both of the linked articles.

As an alternative, I was able to use the Autofill Quick Tile to fill credentials in Ecosia in various websites.

<!-- gh-comment-id:3207599808 --> @SaintPatrck commented on GitHub (Aug 20, 2025): Hi all, Ecosia appears to be a Chromium browser. Chrome, and subsequently all Chromium based browsers, recently changed autofill settings such that 3rd party credential managers MUST be given explicit permission to perform autofill. More details about the change can be found in Google's [Chrome on Android to support third-party autofill services natively](https://android-developers.googleblog.com/2024/10/chrome-3p-autofill-services.html) blog post. We have also updated our help article on [Android Browser Integration](https://bitwarden.com/help/auto-fill-android/#browser-integrations). Although Chrome and Brave are the only browsers we mention by name, the same applies to all Chromium based browsers. That being said, I did a quick check and can confirm that the latest version of Ecosia (12.1.3) **is not** sending autofill requests to Bitwarden. I also searched through Ecosia's settings and I'm unable to locate the Autofill settings that are necessary to enable "Autofill using another service" as described in both of the linked articles. As an alternative, I was able to use the Autofill Quick Tile to fill credentials in Ecosia in various websites.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#88645