6985 on test device

[JohnMcLear]

Test known good device, not locked. Same as you are testing (NFC Ring Dev Ring)

Testing on a Windows box.

I haven't confirmed working on nix yet, heading unit tomorrow if that helps?

Happens when removing ring from ACR reader.

C:\Users\jose\Desktop\node-gp [master ≡ +1 ~2 -0 !]> node .\dist\index.js
(node:93564) UnhandledPromiseRejectionWarning: unexpected response 6985 for 80e602000a05d2760000850000000001
(node:93564) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:93564) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

.cap file is in ./ but I'm pretty sure it's not erroring out on that, seems to be erroring out on some sort of handshake thing.

[benbenbenbenbenben]

80e602 is the package loading, and the dev rings throw 6985 when the package is already loaded.

Can you confirm it's not already loaded with either gpcard.getApplets() or if you have Martin Paljak's gp tool, gp --list?

[PaddeK]

I guess i'am using the same ring (Omni NFC Ring) and also get the 6985 during connect.
In the final step (EXTERNAL AUTHENTICATE Command) the ring is responding with 6985 which
indicates Conditions of use not satisfied.

Any idea? I can help debugging.

[PaddeK]

I had some time at hand and debugged it. In case of the Omni NFC Ring this is not a issue of node-gp.
Problem was detection of card insert/remove of the smartcard lib. I ended up forking node-pcsclite and smartcard to get it all working out (tested with window 7 and omni ring).

Repo with complete example:
https://github.com/PaddeK/omni-ring-example

[JohnMcLear]

whoa, that is crazy, great spot dude!