Hey nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm I’m getting a lot of these types of errors in my apps that use the SDK/NWC/Bitcoin Connect. Can you help?

I tried updating to the latest versions and even creating a new NWC string but still no luck.

Cc: nostr:npub1zk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q0gl6ef nostr:npub1q5sah9f3p9kl7uqdeaqskqwmg74ktxx70e0093dzh4lpzcp3t0mqzxky65

Oof, I just started getting that error on Alby Go.

Reply to this note

Please Login to reply.

Discussion

Ah, good to know it’s not just me. The “no one was listening” part sounds like it could be related to the relay migration. 🤔

nostr:note16vu7gtu0x0fcxlxts42nt9hjgsp86faxymaawh3rqqfkngewkeesflqu2z

Ah maybe…?

I’m just glad that someone is actually listening. 😄🫂⚡️🐝

I updated to the latest version of Alby Hub (1.17.2) and at the moment I’m not getting the error. Will update if I notice anything else.

I think fixed on Alby's end. I was already on the latest version of Hub.