github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-11 10:54:26 -05:00
Code Issues 1.1k Packages Projects Releases 124 Wiki Activity

[GH-ISSUE #1394] Bitwarden not recognising Edge Canary browser on Android #7315

New Issue
Closed
opened 2026-04-10 23:47:59 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-10 23:47:59 -05:00
Owner
Copy Link

Originally created by @danmac on GitHub (May 7, 2021).
Original GitHub issue: https://github.com/bitwarden/android/issues/1394

Describe the Bug

Bitwarden doesn't recognise the new Edge Canary browser on Android as a web browser.

Steps To Reproduce

  1. Download Edge Canary from Play Store
  2. Open any website with a password field
  3. Click Auto-fill with Bitwarden

Expected Result

Bitwarden searches for the web site you are viewing and displays the result for that web site

Actual Result

Bitwarden searches for com.microsoft.emmx.canary or something similar, you then have to manually search for the web site

Screenshots or Videos

Environment

  • Device: Pixel 4 XL
  • Operating system: Android 11
  • Build Version RQ2A.210405.005
  • Is this a Beta release? N

Additional Context

Originally created by @danmac on GitHub (May 7, 2021). Original GitHub issue: https://github.com/bitwarden/android/issues/1394 <!-- Comment: Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> ## Describe the Bug <!-- Comment: A clear and concise description of what the bug is. --> Bitwarden doesn't recognise the new Edge Canary browser on Android as a web browser. ## Steps To Reproduce <!-- Comment: How can we reproduce the behavior: --> 1. Download Edge Canary from Play Store 2. Open any website with a password field 3. Click Auto-fill with Bitwarden ## Expected Result <!-- Comment: A clear and concise description of what you expected to happen. --> Bitwarden searches for the web site you are viewing and displays the result for that web site ## Actual Result <!-- Comment: A clear and concise description of what is happening. --> Bitwarden searches for com.microsoft.emmx.canary or something similar, you then have to manually search for the web site ## Screenshots or Videos <!-- Comment: If applicable, add screenshots and/or a short video to help explain your problem. --> ## Environment - Device: Pixel 4 XL - Operating system: Android 11 - Build Version RQ2A.210405.005 - Is this a Beta release? N ## Additional Context <!-- Comment: Add any other context about the problem here. -->
GiteaMirror commented 2026-04-10 23:48:01 -05:00
Author
Owner
Copy Link

@contribucious commented on GitHub (May 7, 2021):

Hello @danmac,
 

Please see PR https://github.com/bitwarden/mobile/pull/1370:

add package for support Microsoft Edge Beta/Canary/Dev version.

(note: the Beta version doesn't exist at the moment but has already been added in advance.)
 

➡️ This PR was recently merged, so it will be available in the next release. 👍
 

See also the remark that @djsmith85 made here: 😉

@fabis94 Glad I could help. Could you please close the issue. It saves the Devs from going through solved issues.

Thanks. 👍

<!-- gh-comment-id:834628925 --> @contribucious commented on GitHub (May 7, 2021): Hello @danmac, &nbsp; Please see PR https://github.com/bitwarden/mobile/pull/1370: > add package for support Microsoft Edge Beta/Canary/Dev version. _(note: the Beta version doesn't exist at the moment but has already been added in advance.)_ &nbsp; :arrow_right: This PR was recently merged, so it will be available in the next release. :thumbsup: &nbsp; ___ See also the remark that @djsmith85 made [here](https://github.com/bitwarden/mobile/issues/1393#issuecomment-832855105): :wink: > @fabis94 Glad I could help. Could you please close the issue. It saves the Devs from going through solved issues. Thanks. :thumbsup:
GiteaMirror commented 2026-04-10 23:48:02 -05:00
Author
Owner
Copy Link

@xiaoyuin commented on GitHub (May 17, 2021):

Hello @contribucious , I tested with newest Bitwarden (2.10.0) and it still doesn't work for Edge canary. Could you please take a look again if the PR itself really works or some other code changes are needed as well? :)

<!-- gh-comment-id:841992406 --> @xiaoyuin commented on GitHub (May 17, 2021): Hello @contribucious , I tested with newest Bitwarden (2.10.0) and it still doesn't work for Edge canary. Could you please take a look again if the PR itself really works or some other code changes are needed as well? :)
GiteaMirror commented 2026-04-10 23:48:03 -05:00
Author
Owner
Copy Link

@wight554 commented on GitHub (Jun 7, 2021):

Hello @contribucious , I tested with newest Bitwarden (2.10.0) and it still doesn't work for Edge canary. Could you please take a look again if the PR itself really works or some other code changes are needed as well? :)

Can confirm it's still broken

<!-- gh-comment-id:856144456 --> @wight554 commented on GitHub (Jun 7, 2021): > Hello @contribucious , I tested with newest Bitwarden (2.10.0) and it still doesn't work for Edge canary. Could you please take a look again if the PR itself really works or some other code changes are needed as well? :) Can confirm it's still broken
GiteaMirror commented 2026-04-10 23:48:04 -05:00
Author
Owner
Copy Link

@contribucious commented on GitHub (Jun 8, 2021):

@xiaoyuin (@wight554) Hello. Really sorry, could not answer before (very busy at the moment).

➡️ Yes, the PR of @laymanZ is correct regarding the addition of browser support (I mean … the package name is com.microsoft.emmx.canary and the "resource-id" is indeed equal to url_bar as visible on the screenshot n°1 below). So, this line for ex. is indeed correct.

For my part, enabling "Auto-fill Service" (i.e. Autofill Framework) + "Use Accessibility" (i.e. Accessibility Service) + "Use Draw-Over" in Bitwarden settings, I have no problem to use it, see screenshots n°2 and n°3 (additional note: github.com was successfully detected).

BUT … only the accessibility service seems to be used (see screenshot n°4), unlike the latest stable version of Chrome which is the 91.0.4472.88 (see screenshot n°5).

↪️ The situation should be further analyzed then (to see if the problem lies with Bitwarden or Edge Canary, etc.). See with the team therefore (@mportune-bw, @cscharf, …), specifying the precise type of your problem (i.e. what you mean exactly by "doesn't work"), whether you use Autofill Framework, Accessibility Service or both, if the "Draw-Over" permission has been given (in Bitwarden settings > "Auto-fill Services"), your device info (model, …) and version of Android / Edge Canary / Bitwarden, etc. (open another issue if necessary). Same remark for you @wight554. 😉
 

My context

  • Edge Canary 93.0.910.0 (the latest version to date)
  • Bitwarden 2.10.0 (the latest stable version)*
  • Samsung Galaxy J5 2017, on Android 9.

* Tested both with Autofill Framework + Accessibility Service and with Accessibility Service only. Regarding the use of Autofill Framework alone, it is "normal" that this doesn't work, this is also the case with Chrome Stable by the way (known situation).
 

Screenshot(s)

Screenshot n°1

Microsoft_Edge_Canary
Edge Canary 93.0.910.0.

<!-- gh-comment-id:856797696 --> @contribucious commented on GitHub (Jun 8, 2021): @xiaoyuin (@wight554) Hello. Really sorry, could not answer before (very busy at the moment). :arrow_right: Yes, [the PR](https://github.com/bitwarden/mobile/pull/1370) of @laymanZ is correct regarding the addition of browser support (I mean … the package name is **com.microsoft.emmx.canary** and the "resource-id" is indeed equal to **url_bar** as visible on the screenshot n°1 below). So, [this line](https://github.com/bitwarden/mobile/blob/afed18908bcd89065275ccf1a7f4fc6be3a646a7/src/Android/Accessibility/AccessibilityHelpers.cs#L59) for ex. is indeed correct. For my part, enabling "Auto-fill Service" (i.e. Autofill Framework) + "Use Accessibility" (i.e. Accessibility Service) + "Use Draw-Over" in Bitwarden settings, I have no problem to use it, see screenshots [n°2](https://user-images.githubusercontent.com/4764956/121185533-7203c080-c866-11eb-8cf1-5b6f155e3526.jpg) and [n°3](https://user-images.githubusercontent.com/4764956/121185570-7a5bfb80-c866-11eb-98d8-69bc5dd8a0a1.jpg) (**additional note:** github.com was successfully detected). **BUT …** only the accessibility service seems to be used (see screenshot [n°4](https://user-images.githubusercontent.com/4764956/121193133-dc6c2f00-c86d-11eb-9142-2209ae8dc007.jpg)), unlike the latest stable version of Chrome which is the 91.0.4472.88 (see screenshot [n°5](https://user-images.githubusercontent.com/4764956/121193156-e1c97980-c86d-11eb-8065-a765ebc4cd3e.jpg)). :arrow_right_hook: The situation should be further analyzed then (to see if the problem lies with Bitwarden or Edge Canary, etc.). See with the team therefore (@mportune-bw, @cscharf, …), specifying the precise type of your problem (i.e. what you mean exactly by "doesn't work"), whether you use Autofill Framework, Accessibility Service or both, if the "Draw-Over" permission has been given (in Bitwarden settings > "Auto-fill Services"), your device info (model, …) and version of Android / Edge Canary / Bitwarden, etc. (open another issue if necessary). Same remark for you @wight554. :wink: &nbsp; ## My context - Edge Canary 93.0.910.0 (the latest version to date) - Bitwarden 2.10.0 (the latest stable version)* - Samsung Galaxy J5 2017, on Android 9. \* Tested both with Autofill Framework + Accessibility Service and with Accessibility Service only. _Regarding the use of Autofill Framework alone, it is "normal" that this doesn't work, this is also the case with Chrome Stable by the way (known situation)._ &nbsp; ## Screenshot(s) **Screenshot n°1** ![Microsoft_Edge_Canary](https://user-images.githubusercontent.com/4764956/121175072-f0f2fc00-c85a-11eb-9c18-980862c9d7ba.png) _Edge Canary 93.0.910.0._
GiteaMirror commented 2026-04-10 23:48:05 -05:00
Author
Owner
Copy Link

@danmac commented on GitHub (Jun 8, 2021):

Thanks for the extra work on this, I can confirm that mine shows the same behaviour as your screenshots. Let me know if you need someone to test anything.

<!-- gh-comment-id:856806248 --> @danmac commented on GitHub (Jun 8, 2021): Thanks for the extra work on this, I can confirm that mine shows the same behaviour as your screenshots. Let me know if you need someone to test anything.
GiteaMirror commented 2026-04-10 23:48:05 -05:00
Author
Owner
Copy Link

@wight554 commented on GitHub (Jun 8, 2021):

in my case I can't see keyboard autofill like in other browsers, accessibility overlay works just fine

<!-- gh-comment-id:856807426 --> @wight554 commented on GitHub (Jun 8, 2021): in my case I can't see keyboard autofill like in other browsers, accessibility overlay works just fine
GiteaMirror commented 2026-04-10 23:48:06 -05:00
Author
Owner
Copy Link

@xiaoyuin commented on GitHub (Jun 10, 2021):

Appreciate for the investigation and detailed reply. By doesn't work I meant neither accessibility service or draw-over was enabled. But it doesn't matter, we have also done some research and now I'm quite sure that you have done everything right. The problem is on the Edge side. Thank you again for the help and all the efforts you have made. :)

<!-- gh-comment-id:858216283 --> @xiaoyuin commented on GitHub (Jun 10, 2021): Appreciate for the investigation and detailed reply. By doesn't work I meant neither accessibility service or draw-over was enabled. But it doesn't matter, we have also done some research and now I'm quite sure that you have done everything right. The problem is on the Edge side. Thank you again for the help and all the efforts you have made. :)
GiteaMirror commented 2026-04-10 23:48:06 -05:00
Author
Owner
Copy Link

@contribucious commented on GitHub (Jun 10, 2021):

@xiaoyuin My pleasure! 👍

<!-- gh-comment-id:858969666 --> @contribucious commented on GitHub (Jun 10, 2021): @xiaoyuin My pleasure! :thumbsup:
GiteaMirror commented 2026-04-10 23:48:07 -05:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/1394

<!-- gh-comment-id:2181543692 --> @vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/1394
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
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#7315
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?