Thread - Nostr Hypermedia

Just doing some quick debugging and I think it's related to relay authorization/subscribing, when I add a key that has some dud relays on its relay list I get the following errors in Logcat (the same number as dud relays): ``` ActivityThread com.koalasat.pokey.debug E Failed to find provider info for .SIGN_EVENT ActivityThread com.koalasat.pokey.debug E Failed to find provider info for .SIGN_EVENT ActivityThread com.koalasat.pokey.debug E Failed to find provider info for .SIGN_EVENT ``` When I add a key with good relays, I don't get this error I'll dig a little more and see if there's an issue/PR to file

↑ Parent

Replies (3)

Biz chebizarro@coinos.io 1 year ago

Digging deeper, it seems to be related to the npub being sent by Pokey to Amber in the "current_user" Intent field for Relay auth. Pokey is sending an empty string which Amber is converting to a hex string and signing the Auth event with, which in turn is being rejected by the Relay, which causes the error. At least *I think so* - because debugging IPC is complicated! When I change the null check in Amber to be isNullOrEmpty() then the error goes away.

KoalaSat koalasat@robosats.org 1 year ago

That's really interesting, thanks is for you work!! But what I am supposed to send if I'm actually using that request to get the npub?

Biz chebizarro@coinos.io 1 year ago

You're welcome, I've been working on NIP-55 integration for a while so I'm always interested in these edge cases. I think the issue lies in the bogus hex key that Amber generates from the empty npub string. It needs more testing with various pubkeys combinations, but changing the null check in Amber fixes the problem for me. I'm happy to raise an issue, the bug is easily reproducible with the right test keys, the only question is which repo - Pokey, Amber or both?