github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #5117] Inline autofill no longer works in Brave Android 15 latest Bitwarden version #14851

New Issue
Closed
opened 2026-04-15 01:00:01 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-15 01:00:01 -05:00
Owner
Copy Link

Originally created by @linucksrox on GitHub (May 1, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5117

Steps To Reproduce

  1. From the previous working version, before the major UI update, have inline autofill enabled and working in Brave browser on Android 15
  2. Upgrade Bitwarden to the latest version
  3. Go to any login page in the Brave browser
  4. Fail to find inline autofill working whether by keyboard autosuggest bar or overlays
  5. Somehow this seems to prevent the quick tile from working as well - see #4586

Expected Result

inline autofill shoulda kept workin'

Actual Result

inline autofill didn't keep workin'

Screenshots or Videos

🤷

Additional Context

No response

Build Version

2025.3.0

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Android 15, latest Graphene OS update build number 2025042500
  • Brave browser 1.77.101

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 @linucksrox on GitHub (May 1, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5117 ### Steps To Reproduce 1. From the previous working version, before the major UI update, have inline autofill enabled and working in Brave browser on Android 15 2. Upgrade Bitwarden to the latest version 3. Go to any login page in the Brave browser 4. Fail to find inline autofill working whether by keyboard autosuggest bar or overlays 5. Somehow this seems to prevent the quick tile from working as well - see #4586 ### Expected Result inline autofill shoulda kept workin' ### Actual Result inline autofill didn't keep workin' ### Screenshots or Videos 🤷 ### Additional Context _No response_ ### Build Version 2025.3.0 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Android 15, latest Graphene OS update build number 2025042500 - Brave browser 1.77.101 ### Issue Tracking Info - [x] 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 app:password-managerbug labels 2026-04-15 01:00:01 -05:00
GiteaMirror commented 2026-04-15 01:00:07 -05:00
Author
Owner
Copy Link

@S-Kakar commented on GitHub (May 1, 2025):

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

<!-- gh-comment-id:2843819350 --> @S-Kakar commented on GitHub (May 1, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-21070
GiteaMirror commented 2026-04-15 01:00:08 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (May 1, 2025):

Hi @linucksrox,

Thanks for opening a separate issue for this. A few questions:

  • Does the generic "Bitwarden My Vault" suggestion ever display?
    Image

  • What type of matching rules, if any, are applied to the results you're expecting?

  • I'm having trouble replicating this on the sites I've tried. Could you provide a couple example sites you're experience this on?

    • I don't believe this is what you're experiencing, but it's worth noting there is one scenario in which I get no suggestions; when I navigate to a site or click on a field while I have text recently copied to the clipboard. In that scenario, the copied text is suggested and no Bitwarden suggestions are shown until I paste or clear the clipboard contents.

  • Are inline suggestions absent regardless of the "Use accessibility" setting state? I'm curious why you believe this interferes with the Quick Tile behavior because the Accessibility service is a completely separate service from Autofill, and they are not triggered or processed the same way.

Inline autofill relies on the OS/browser invoking our service and providing us the data. If thy don't invoke our service we cannot provide suggestions. The Autofill framework DOES NOT provide port, path, and query string information so we can't perform matching on those parts of a URI. This can result in unexpected suggestions appearing and those suggestions will be inconsistent with the Accessibility autofill suggestions.

Accessibility autofill relies on the user clicking the Quick Tile, the foreground app being fillable, and fillable fields can be found. We DO have access to port, path, and query string in most cases, so matching works as expected. We're working on changes (#5116) to improve the user facing messaging so that it doesn't silently fail, as well as fixing a known issue with checking for ports.

If you are willing and able to grab some logs for me; I opened #5120 (builds), with breadcrumbs that will report when our autofill service is invoked, and the number of results returned to the system. That will be a good start to identify where the issue is.

If you have the means to view logcat, you can filter for the tags, AutofillProcessorImpl and FilledDataBuilderImpl. Several other things are logged, but those are the only ones we're concerned with for now.

The other option is to use our "Flight Recorder" feature. It is still disabled via a feature flag, so in order to use it you'll have to install a dev build and enable it. Steps are below.

Steps to capture logs with Flight Recorder
  • Open the debug menu by tapping 3 times with 3 fingers anywhere in the app (except a text field). If a physical keyboard is connected you can also press SHIFT ~ to open the debug menu.
  • Enable the Flight Recorder switch.
  • Navigate to Settings > About and you will see the new "Flight recorder" option. Turn it on.
  • Navigate to a page you expect inline autofill to provide suggestions for and tap on a field. It may be worth doing this on a few different sites and fields.
  • Navigate back to Bitwarden.
  • Turn off "Flight recorder" (in Settings)
  • Click "View recorded logs"
  • "Share" the logs using the overflow option. This generates an archive that contains a .txt file.
  • You can post them here after removing any HTTP logs since they are not relevant.
Example Flight Recorder logs
2025-05-01 14:04:41:101 – DEBUG – VaultUnlockedNavBarScreen destination changed: vault in vault_graph
2025-05-01 14:04:44:153 – DEBUG – App is backgrounded
2025-05-01 14:04:44:163 – DEBUG – Autofill request processing has started.
2025-05-01 14:04:44:179 – DEBUG – Autofill request is fillable. Proceeding with fulfillment.
2025-05-01 14:04:44:189 – DEBUG – Generated 1 filled partitions and added 1 inline suggestions.
2025-05-01 14:04:44:202 – DEBUG – Done processing autofill request with 1 partitions.
2025-05-01 14:05:24:248 – DEBUG – Autofill request processing has started.
2025-05-01 14:05:24:264 – DEBUG – Autofill request is fillable. Proceeding with fulfillment.
2025-05-01 14:05:24:270 – DEBUG – Generated 1 filled partitions and added 1 inline suggestions.
2025-05-01 14:05:24:285 – DEBUG – Done processing autofill request with 1 partitions.
2025-05-01 14:07:08:315 – DEBUG – App is foregrounded
2025-05-01 14:07:09:552 – DEBUG – VaultUnlockedNavBarScreen destination changed: settings in settings_graph
2025-05-01 14:07:09:555 – DEBUG – VaultUnlockedNavBarScreen destination changed: settings_about in settings_graph
<!-- gh-comment-id:2845580495 --> @SaintPatrck commented on GitHub (May 1, 2025): Hi @linucksrox, Thanks for opening a separate issue for this. A few questions: - Does the generic "Bitwarden My Vault" suggestion ever display? <img width="420" alt="Image" src="https://github.com/user-attachments/assets/74460615-7a46-4dcc-8e96-dfb3562a158f" /> - What type of matching rules, if any, are applied to the results you're expecting? - I'm having trouble replicating this on the sites I've tried. Could you provide a couple example sites you're experience this on? - I don't believe this is what you're experiencing, but it's worth noting there is one scenario in which I get no suggestions; when I navigate to a site or click on a field while I have text recently copied to the clipboard. In that scenario, the copied text is suggested and no Bitwarden suggestions are shown until I paste or clear the clipboard contents. - Are inline suggestions absent regardless of the "Use accessibility" setting state? I'm curious why you believe this interferes with the Quick Tile behavior because the Accessibility service is a completely separate service from Autofill, and they are not triggered or processed the same way. **Inline autofill** relies on the OS/browser invoking our service and providing us the data. If thy don't invoke our service we cannot provide suggestions. The Autofill framework DOES NOT provide port, path, and query string information so we can't perform matching on those parts of a URI. This can result in unexpected suggestions appearing and those suggestions will be inconsistent with the Accessibility autofill suggestions. **Accessibility autofill** relies on the user clicking the Quick Tile, the foreground app being fillable, and fillable fields can be found. We DO have access to port, path, and query string in most cases, so matching works as expected. We're working on changes (#5116) to improve the user facing messaging so that it doesn't silently fail, as well as fixing a known issue with checking for ports. If you are willing and able to grab some logs for me; I opened #5120 ([builds](https://github.com/bitwarden/android/actions/runs/14781025041)), with breadcrumbs that will report when our autofill service is invoked, and the number of results returned to the system. That will be a good start to identify where the issue is. If you have the means to view `logcat`, you can filter for the tags, `AutofillProcessorImpl` and `FilledDataBuilderImpl`. Several other things are logged, but those are the only ones we're concerned with for now. The other option is to use our "Flight Recorder" feature. It is still disabled via a feature flag, so in order to use it you'll have to install a [dev build](https://github.com/bitwarden/android/actions/runs/14781025041/artifacts/3046344700) and enable it. Steps are below. <details> <summary>Steps to capture logs with Flight Recorder</summary> - Open the debug menu by tapping 3 times with 3 fingers anywhere in the app (except a text field). If a physical keyboard is connected you can also press `SHIFT ~` to open the debug menu. - Enable the Flight Recorder switch. - Navigate to Settings > About and you will see the new "Flight recorder" option. Turn it on. - Navigate to a page you expect inline autofill to provide suggestions for and tap on a field. It may be worth doing this on a few different sites and fields. - Navigate back to Bitwarden. - Turn off "Flight recorder" (in Settings) - Click "View recorded logs" - "Share" the logs using the overflow option. This generates an archive that contains a `.txt` file. - You can post them here after removing any HTTP logs since they are not relevant. </details> <details> <summary>Example Flight Recorder logs</summary ``` 2025-05-01 14:04:41:101 – DEBUG – VaultUnlockedNavBarScreen destination changed: vault in vault_graph 2025-05-01 14:04:44:153 – DEBUG – App is backgrounded 2025-05-01 14:04:44:163 – DEBUG – Autofill request processing has started. 2025-05-01 14:04:44:179 – DEBUG – Autofill request is fillable. Proceeding with fulfillment. 2025-05-01 14:04:44:189 – DEBUG – Generated 1 filled partitions and added 1 inline suggestions. 2025-05-01 14:04:44:202 – DEBUG – Done processing autofill request with 1 partitions. 2025-05-01 14:05:24:248 – DEBUG – Autofill request processing has started. 2025-05-01 14:05:24:264 – DEBUG – Autofill request is fillable. Proceeding with fulfillment. 2025-05-01 14:05:24:270 – DEBUG – Generated 1 filled partitions and added 1 inline suggestions. 2025-05-01 14:05:24:285 – DEBUG – Done processing autofill request with 1 partitions. 2025-05-01 14:07:08:315 – DEBUG – App is foregrounded 2025-05-01 14:07:09:552 – DEBUG – VaultUnlockedNavBarScreen destination changed: settings in settings_graph 2025-05-01 14:07:09:555 – DEBUG – VaultUnlockedNavBarScreen destination changed: settings_about in settings_graph ``` </details>
GiteaMirror commented 2026-04-15 01:00:09 -05:00
Author
Owner
Copy Link

@linucksrox commented on GitHub (May 2, 2025):

Great questions, let me start by answering those real quick and hopefully clarifying what I meant about inline autofill vs. the quick tile.

Does the generic "Bitwarden My Vault" suggestion ever display?

No, when using the Brave browser I do not see anything Bitwarden related, and I've never seen what you're showing in that screenshot.

What type of matching rules, if any, are applied to the results you're expecting?

I have Default URI match detection set to Host since I self-host a lot of things using subdomains and the out-of-the-box Base domain setting gives too many results :)

Could you provide a couple example sites you're experience this on?

It seems to be 100% of sites I visit in the Brave browser, with no exceptions. Let's take LinkedIn for example. I'm using Gboard by the way as my keyboard BTW. Here's what happens in Brave when going to the login page, and here's the same exact URL in Firefox. In Brave, I never get that Bitwarden icon to unlock the vault and autofill the password.

I don't think this has anything to do with what's in my clipboard, as you can see in the screenshots I have nothing in the clipboard but Bitwarden gets "triggered" properly from Firefox, just not from Brave. Although I don't recall having any issues in other apps where Bitwarden works as expected even if I do have something in the clipboard.

Image
Image

Are inline suggestions absent regardless of the "Use accessibility" setting state? I'm curious why you believe this interferes with the Quick Tile behavior because the Accessibility service is a completely separate service from Autofill, and they are not triggered or processed the same way.

Yes, I tried disabling this setting but it still doesn't help. I don't believe Inline Autofill is necessarily related to the Quick Tile, but I am just observing the fact that when Inline Autofill doesn't work in Brave, that seems to correlate directly to the Quick Tile also not working in Brave. So I would just say that both Bitwarden functions/features are failing to work properly with the Brave browser currently. I honestly don't care about the Quick Tile and instead rely heavily on Inline Autofill which is far more convenient for me, so if it helps, forget I said anything about the Quick Tile :)

Regarding your additional explanation of how Inline Autofill works (and thank you for that by the way), that makes sense. However, what's odd to me and others is that the OLD Bitwarden app had no issues with the Brave browser. The NEW Bitwarden app has this issue. So I can say with a high level of confidence (not 100% but I'm pretty convinced) that this regression is the result of a change on the Bitwarden side, not a new change in the Brave browser. That's not to say something in Brave isn't invoking this functionality properly, but again it worked on the old version of the App before the big UI update, and now it does not.

I'll try out the breadcrumbs build and see what logs I can get and report back after I have a chance.

Also, thank you for the detailed feedback and great questions! I look forward to solving this one!

<!-- gh-comment-id:2846095958 --> @linucksrox commented on GitHub (May 2, 2025): Great questions, let me start by answering those real quick and hopefully clarifying what I meant about inline autofill vs. the quick tile. > Does the generic "Bitwarden My Vault" suggestion ever display? No, when using the Brave browser I do not see anything Bitwarden related, and I've never seen what you're showing in that screenshot. > What type of matching rules, if any, are applied to the results you're expecting? I have Default URI match detection set to Host since I self-host a lot of things using subdomains and the out-of-the-box Base domain setting gives too many results :) > Could you provide a couple example sites you're experience this on? It seems to be 100% of sites I visit in the Brave browser, with no exceptions. Let's take LinkedIn for example. I'm using Gboard by the way as my keyboard BTW. Here's what happens in Brave when going to the login page, and here's the same exact URL in Firefox. In Brave, I never get that Bitwarden icon to unlock the vault and autofill the password. I don't think this has anything to do with what's in my clipboard, as you can see in the screenshots I have nothing in the clipboard but Bitwarden gets "triggered" properly from Firefox, just not from Brave. Although I don't recall having any issues in other apps where Bitwarden works as expected even if I do have something in the clipboard. ![Image](https://github.com/user-attachments/assets/90808356-ee70-43bb-99de-497928751f3a) ![Image](https://github.com/user-attachments/assets/f160cc32-43cf-48a2-b7ad-29c979ebb040) > Are inline suggestions absent regardless of the "Use accessibility" setting state? I'm curious why you believe this interferes with the Quick Tile behavior because the Accessibility service is a completely separate service from Autofill, and they are not triggered or processed the same way. Yes, I tried disabling this setting but it still doesn't help. I don't believe Inline Autofill is necessarily related to the Quick Tile, but I am just observing the fact that **when** Inline Autofill doesn't work in Brave, that seems to correlate directly to the Quick Tile **also** not working in Brave. So I would just say that both Bitwarden functions/features are failing to work properly with the Brave browser currently. I honestly don't care about the Quick Tile and instead rely heavily on Inline Autofill which is far more convenient for me, so if it helps, forget I said anything about the Quick Tile :) Regarding your additional explanation of how Inline Autofill works (and thank you for that by the way), that makes sense. However, what's odd to me and others is that the OLD Bitwarden app had no issues with the Brave browser. The NEW Bitwarden app has this issue. So I can say with a high level of confidence (not 100% but I'm pretty convinced) that this regression is the result of a change on the Bitwarden side, not a new change in the Brave browser. That's not to say something in Brave isn't invoking this functionality properly, but again it worked on the old version of the App before the big UI update, and now it does not. I'll try out the breadcrumbs build and see what logs I can get and report back after I have a chance. Also, thank you for the detailed feedback and great questions! I look forward to solving this one!
GiteaMirror commented 2026-04-15 01:00:09 -05:00
Author
Owner
Copy Link

@linucksrox commented on GitHub (May 2, 2025):

Update - I installed the dev build 2025.5.0 version 20135 and updated the inline autofill services to use BitWarden dev. I logged in, and changed the setting to do Host matching. I still get the same behavior (works in Firefox, does not work in Brave). Subsequently, I get ADB logs from Firefox, but NOTHING from brave.

When it works in Firefox, I get what is probably expected like this

05-01 21:26:22.792 24307 24307 D AutofillProcessorImpl: Autofill request processing has started.
05-01 21:26:22.806 24307 24307 D AutofillProcessorImpl: Autofill request is fillable. Proceeding with fulfillment.
05-01 21:26:23.862 24307 24307 D FilledDataBuilderImpl: Generated 1 filled partitions and added 1 inline suggestions.
05-01 21:26:23.872 24307 24307 D AutofillProcessorImpl: Done processing autofill request with 1 partitions.

Brave just keeps ghosting me though :)

I also enabled the Flight recorder and tried going to 3 or 4 different sites in Brave that should autofill but did not. Here's the full log from that (pretty sparse unfortunately):

Bitwarden Android
Log Start Time: 2025-05-01 21:32:38:807
Log Duration: 1h
App Version: 2025.5.0 (20135)
Build: debug/standard
Operating System: 15 (35)
Device: google Pixel 6a
2025-05-01 21:32:38:821 – DEBUG – RootNavScreen destination changed: VaultUnlockedNavBar in vault_unlocked_graph
2025-05-01 21:32:38:930 – DEBUG – VaultUnlockedNavBarScreen destination changed: settings_about in settings_graph
2025-05-01 21:32:41:019 – DEBUG – App is backgrounded
2025-05-01 21:33:29:879 – DEBUG – App is foregrounded

One last thing I thought of, since this is Graphene OS, I enabled "Exploit protection compatibility mode" for Brave and restarted it, but still doesn't work :(

<!-- gh-comment-id:2846119156 --> @linucksrox commented on GitHub (May 2, 2025): Update - I installed the dev build 2025.5.0 version 20135 and updated the inline autofill services to use BitWarden dev. I logged in, and changed the setting to do Host matching. I still get the same behavior (works in Firefox, does not work in Brave). Subsequently, I get ADB logs from Firefox, but NOTHING from brave. When it works in Firefox, I get what is probably expected like this ``` 05-01 21:26:22.792 24307 24307 D AutofillProcessorImpl: Autofill request processing has started. 05-01 21:26:22.806 24307 24307 D AutofillProcessorImpl: Autofill request is fillable. Proceeding with fulfillment. 05-01 21:26:23.862 24307 24307 D FilledDataBuilderImpl: Generated 1 filled partitions and added 1 inline suggestions. 05-01 21:26:23.872 24307 24307 D AutofillProcessorImpl: Done processing autofill request with 1 partitions. ``` Brave just keeps ghosting me though :) I also enabled the Flight recorder and tried going to 3 or 4 different sites in Brave that should autofill but did not. Here's the full log from that (pretty sparse unfortunately): ``` Bitwarden Android Log Start Time: 2025-05-01 21:32:38:807 Log Duration: 1h App Version: 2025.5.0 (20135) Build: debug/standard Operating System: 15 (35) Device: google Pixel 6a 2025-05-01 21:32:38:821 – DEBUG – RootNavScreen destination changed: VaultUnlockedNavBar in vault_unlocked_graph 2025-05-01 21:32:38:930 – DEBUG – VaultUnlockedNavBarScreen destination changed: settings_about in settings_graph 2025-05-01 21:32:41:019 – DEBUG – App is backgrounded 2025-05-01 21:33:29:879 – DEBUG – App is foregrounded ``` One last thing I thought of, since this is Graphene OS, I enabled "Exploit protection compatibility mode" for Brave and restarted it, but still doesn't work :(
GiteaMirror commented 2026-04-15 01:00:10 -05:00
Author
Owner
Copy Link

@T00rk commented on GitHub (May 21, 2025):

...

<!-- gh-comment-id:2899506172 --> @T00rk commented on GitHub (May 21, 2025): ...
GiteaMirror commented 2026-04-15 01:00:12 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (May 22, 2025):

Thanks for nudging this @T00rk. And thank you, @linucksrox, for the logs and details.

I've never seen what you're showing in that screenshot.

The "Bitwarden Vault is locked" option in your keyboard is the same inline autofill suggestion from my screenshot, but in different states. My vault was unlocked and no results were found for the site. Your vault was locked which is why it says "Vault is locked" instead. I should have included more context in my screenshot to be clear what I was referring to. Apologies for that. Nonetheless, I'm glad to see it is appearing in other apps, or we would have much larger problems. 😅

The logs you captured are very telling. They're indicating that either Brave is not invoking the Autofill framework correctly, or that the OS is not delivering the request to Bitwarden. Unfortunately, both of those are out of our control. If we don't receive a request, we have nothing to process. 😞

What makes this even more confusing is that it works in Brave on Stock Android 15 and you're seeing success with other browsers in GrapheneOS. I would expect those cases to be mutually exclusive unless there are differences in the Brave builds for each OS. I suggest filing a bug with Brave and/or Graphene if you have not already. They may be able to provide some insight into why the behavior is different.

That being said, the one major difference between the MAUI (<=2024.6.0) and native (>=2024.6.1-beta) Bitwarden app is the overlay that would be drawn on the screen when Accessibility was enabled. I believe this is causing some general confusion. Our Accessibility overlay is different than the overlay triggered by Autofill when Inline is disabled but looked and behaved very similar. The Accessibility overlay we drew is absent from the native apps. That means, instead of seeing suggestions pop up near the field like you would in the MAUI app with Accessibility enabled, you must click the Quick Tile to scan the screen and launch Bitwarden.

<!-- gh-comment-id:2902672243 --> @SaintPatrck commented on GitHub (May 22, 2025): Thanks for nudging this @T00rk. And thank you, @linucksrox, for the logs and details. >I've never seen what you're showing in that screenshot. The "Bitwarden Vault is locked" option in your keyboard is the same inline autofill suggestion from my screenshot, but in different states. My vault was unlocked and no results were found for the site. Your vault was locked which is why it says "Vault is locked" instead. I should have included more context in my screenshot to be clear what I was referring to. Apologies for that. Nonetheless, I'm glad to see it **is** appearing in other apps, or we would have much larger problems. 😅 The logs you captured are very telling. They're indicating that either Brave is not invoking the Autofill framework correctly, or that the OS is not delivering the request to Bitwarden. Unfortunately, both of those are out of our control. If we don't receive a request, we have nothing to process. 😞 What makes this even more confusing is that it works in Brave on Stock Android 15 and you're seeing success with other browsers in GrapheneOS. I would expect those cases to be mutually exclusive unless there are differences in the Brave builds for each OS. I suggest filing a bug with Brave and/or Graphene if you have not already. They may be able to provide some insight into why the behavior is different. That being said, the one major difference between the MAUI (<=[2024.6.0](https://github.com/bitwarden/android/releases/tag/v2024.6.0)) and native (>=[2024.6.1-beta](https://github.com/bitwarden/android/releases/tag/v2024.6.1)) Bitwarden app is the overlay that would be drawn on the screen when Accessibility was enabled. I believe this is causing some general confusion. Our Accessibility overlay is different than the overlay triggered by Autofill when Inline is disabled but looked and behaved very similar. The Accessibility overlay we drew is absent from the native apps. That means, instead of seeing suggestions pop up near the field like you would in the MAUI app with Accessibility enabled, you **must** click the Quick Tile to scan the screen and launch Bitwarden.
GiteaMirror commented 2026-04-15 01:00:13 -05:00
Author
Owner
Copy Link

@T00rk commented on GitHub (May 23, 2025):

This workaround works for me

https://github.com/brave/brave-browser/issues/36553#issuecomment-2555045732

<!-- gh-comment-id:2904279608 --> @T00rk commented on GitHub (May 23, 2025): This workaround works for me https://github.com/brave/brave-browser/issues/36553#issuecomment-2555045732
GiteaMirror commented 2026-04-15 01:00:14 -05:00
Author
Owner
Copy Link

@linucksrox commented on GitHub (May 28, 2025):

Yes, WOOT that solves it for me as well. It was Brave browser the whole time. Thanks @SaintPatrck for helping dig into the logs which pointed us in the right direction, and thanks @T00rk for bumping and finding the solution!

For posterity:

  1. brave://flags -> #enable-autofill-virtual-view-structure -> Enable without compatibility check
  2. relaunch
  3. Brave Settings -> Autofill services -> Autofill using another service
<!-- gh-comment-id:2916484582 --> @linucksrox commented on GitHub (May 28, 2025): Yes, WOOT that solves it for me as well. It was Brave browser the whole time. Thanks @SaintPatrck for helping dig into the logs which pointed us in the right direction, and thanks @T00rk for bumping and finding the solution! For posterity: 1. `brave://flags` -> `#enable-autofill-virtual-view-structure` -> `Enable without compatibility check` 2. relaunch 3. Brave Settings -> Autofill services -> Autofill using another service
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#14851
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?