- From: glococo via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Aug 2020 10:47:15 +0000
- To: public-web-nfc@w3.org
glococo has just created a new issue for https://github.com/w3c/web-nfc: == Chrome, nfc-list and ACR122 == Hi everyone. I want to work in desktop with the ACR122 nfc pad but It seems to not be detected by Chromium, Chrome (Beta/Dev) in Ubuntu. My current setup seems to work from console: ```guillermo@lab:~$ nfc-list -v nfc-list uses libnfc 1.7.1 NFC device: ACS / ACR122U PICC Interface opened 1 ISO14443A passive target(s) found: ISO/IEC 14443A (106 kbps) target: ATQA (SENS_RES): 00 44 * UID size: double * bit frame anticollision supported UID (NFCID1): 04 98 f9 ba 53 65 80 SAK (SEL_RES): 00 * Not compliant with ISO/IEC 14443-4 * Not compliant with ISO/IEC 18092 Fingerprinting based on MIFARE type Identification Procedure: * MIFARE Ultralight * MIFARE Ultralight C Other possible matches based on ATQA & SAK values: 0 Felica (212 kbps) passive target(s) found. 0 Felica (424 kbps) passive target(s) found. 0 ISO14443B passive target(s) found. 0 ISO14443B' passive target(s) found. 0 ISO14443B-2 ST SRx passive target(s) found. 0 ISO14443B-2 ASK CTx passive target(s) found. 0 Jewel passive target(s) found. guillermo@tfe152:~$ pcsc_scan Using reader plug'n play mechanism Scanning present readers... 0: ACS ACR122U 00 00 Tue Aug 11 11:44:52 2020 Reader 0: ACS ACR122U 00 00 Event number: 5 Card state: Card inserted, ATR: 3B 00 ATR: 3B 00 + TS = 3B --> Direct Convention + T0 = 00, Y(1): 0000, K: 0 (historical bytes) \ guillermo@lab:~$ ``` In Chrome I get in web-nfc sample: ``` User clicked scan button Argh! NotAllowedError: NFC permission request denied. ``` Any help is really appreciated. Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/595 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 August 2020 10:47:16 UTC