search

nunchuk-io / tap-protocol

Coinkite Tap Protocol
MIT License
15 stars 4 forks source link

Adding a Tapsigner that was previously setup #14

Open mattcrv opened 6 months ago

mattcrv commented 6 months ago

I set up a Tapsigner using Nunchuk months ago to try it out, uninstalled the app in the meantime, and shelved the Tapsigner. I'm now picking it back up, but when I try once again adding it as a key, nothing happens:

https://github.com/nunchuk-io/tap-protocol/assets/93796166/33cfb723-6356-4ce7-a9ec-891959046d34

hugohn commented 6 months ago

Can you try with another phone? If it doesn't work on another phone, the hardware itself might have been damaged.

The NFC code hasn't changed for quite a while.

mattcrv commented 6 months ago

Tried on another phone, nothing:

https://github.com/nunchuk-io/tap-protocol/assets/93796166/a693944f-6a29-46ef-8c27-23cac67e8897

Are these supposed to look any different for a Tapsigner that was already set up in the past?

IMG_0302 IMG_0300

Happy to reach out to Coinkite instead, but I don't have an NFC reader for my Mac and can't try it on Sparrow, so I can't distinguish what might be a Nunchuk issue from what is a Tapsigner issue.

hugohn commented 6 months ago

Another thing you can try is the Android app. We publish Android APKs for old releases going back to Jan 2023: https://github.com/nunchuk-io/nunchuk-android/releases

The reason I suspect it's a hardware issue is because (a) we haven't made any major changes w.r.t. NFC for quite a while and (b) if there were an issue, we would likely have heard of similar reports out in the field (Tapsigners are very popular). Yours is the only one so far.

mattcrv commented 6 months ago

Gotcha. Unfortunately, I don't have an Android phone to test it out. I'll email Coinkite to see if it's a known hardware issue. Thanks!