Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome Version and Android #70

Closed
puttley opened this issue Oct 21, 2019 · 7 comments
Closed

Chrome Version and Android #70

puttley opened this issue Oct 21, 2019 · 7 comments

Comments

@puttley
Copy link

puttley commented Oct 21, 2019

Hello - I have a webUSB device that works perfectly with the latest versions of Chrome on Win 10 and Mac OS. However, the newest version of Chrome for Android will no longer work...earlier versions did.

When attempting to connect using an Android device, I get a SecurityError: Access denied message. My device will show up in the device selection window, but when I select it and attempt to connect I get a NotFoundError: No device selected.

Is there a known issue with Android and the latest version for Chrome 77.0.3865.116 ?

@reillyeon
Copy link
Collaborator

This is a known issue with Chrome 77 and has been fixed in Chrome 78 (issue 1009362). You can verify this issue has been fixed by installing Chrome Beta from the Google Play Store. According to the schedule Chrome 78 should be released to stable-channel users shortly.

@puttley
Copy link
Author

puttley commented Oct 21, 2019

Thanks for the prompt reply. I downloaded and installed Chrome Beta 78.0.3904.62. The webUSB device appears in the device list window, but once I select it and attempt to connect, Chrome crashes and closes. Still, no issues with the latest versions of Chrome on Win 10, Mac and Chromebook - only Android.

@reillyeon
Copy link
Collaborator

I've filed an issue internally to track this. Thanks for checking.

@puttley
Copy link
Author

puttley commented Oct 22, 2019 via email

@puttley
Copy link
Author

puttley commented Nov 1, 2019

Has there been an update on this issue?

@reillyeon
Copy link
Collaborator

The issue has been fixed in Chrome 78.0.3904.90 and is rolling out to stable-channel now.

@puttley
Copy link
Author

puttley commented Nov 2, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants