DOMException: The interface number provided is not supported by the device in its current configuration.
Reported by
sudarsha...@gmail.com,
Nov 17
|
|||
Issue description
Chrome Version : 70.0.3538.102
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox:
IE/Edge:
What steps will reproduce the problem?
1. AFTER SELECTING SMART CARD READER
2. Code is
-------------------------------*******************------------------------------
<script>
var usbd = {};
(function() {
'use strict';
usbd.authorize = function(){
var device;
navigator.usb.requestDevice({ filters: [{ vendorId: 0x072F }] })
.then(selectedDevice => {
device = selectedDevice;
console.log(device);
return device.open(); // Begin a session.
})
.then(() => device.selectConfiguration(1)) // Select configuration #1 for the device.
.then(() => device.claimInterface(0)) // Request exclusive control over interface #2.
.then(() => device.controlTransferOut({
requestType: 'class',
recipient: 'interface',
request: 0x22,
value: 0x01,
index: 0x02})) // Ready to receive data
.then(() => device.transferIn(5, 64)) // Waiting for 64 bytes of data from endpoint #5.
.then(result => {
let decoder = new TextDecoder();
console.log('Received: ' + decoder.decode(result.data));
})
.catch(error => { console.log(error); });
};
})();
</script>
<button id="connect" onclick="usbd.authorize()" >connect</button>
-------------------------------*******************------------------------------
What is the expected result?
What happens instead of that?
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36
,
Nov 19
Tried testing the issue on chrome reported version# 70.0.3538.106 using Windows-10 with steps mentioned below: 1) Launched chrome reported version and created '.html' file with script provided in comment# 0 2) Dragged and dropped the file created in step-1 into New Tab Page, able to 'connect' button on the page 3) Clicked on 'connect' button, a prompt message shows "No compatible devices found" message found @Reporter: Please find the attached screencast for your reference, if possible could you please provide consistent reproducible steps with actual and excepted behavior which help in further triaging it in better way. Thanks!
,
Dec 13
Closing issue due to lack of information provided. If the issue still exists please open a new issue with the reproduction steps. |
|||
►
Sign in to add a comment |
|||
Comment 1 by krajshree@chromium.org
, Nov 18