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

Reply to this note

Please Login to reply.

Discussion

Getting the same error in Alby Go. I’m talking to nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x on Discord about it.

Could it be a relay problem?

I have a self hosted Alby Hub and thought it was my own issue until I saw this note. I’m not sure how relays play in to wallet connections but must be on their end if we’re all having the issue.

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

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.

Browser extension is now working (I was having an issue there too)

Ok, I think it’s fixed.

I still get the error message

The exact same one?

I don't get the same message in alby go anymore, but when I try to send a transaction I'm getting: FAILURE_REASON_NO_ROUTE. Maybe a problem on my end?

It’s a routing error so this is different. Can you check your node page? Who do you have channels with? Do you know if the recipient is online to receive the payment?

I'm using Megalith LSP and it's online. I tried sending sats to a different address and it worked. Is it fair to assume the issue isn't on my end?

That’s right, not on your end.

does this persist? do you still see this error?

I stopped seeing it just now coincidentally. Not sure if y’all did anything.

Tested here: https://bullishbulletin.vercel.app