Thanks for the sats, received this when trying to send them (DM didn’t seem to work) Failed to decode NWC Wallet response JSON. Error: typeMismatch(damus.WalletConnect.Response.Result.ResultType, Swift.DecodingError.Context(codingPath: [], debugDescription: "result_type error is unknown", underlyingError: nil)) @Damus @Rizful.com

@Damus did something change recently with Damus NWC implementation? I'm seeing this error also with a Rizful NWC code... also finding that the Copy Technical Information button isn't working as far as I can tell

@TAM | FAFO Rocks you could also try with Yakihonne, which doesn't show any error messages when using Rizful NWC.

@TAM | FAFO Rocks @Damus Oh, it's this issue:

GitHub

Bug: Error when receiving get_info response via NWC · Issue #3262 · damus-io/damus

This is a rather subtle bug and I'm not surprised that your testing hasn't caught it yet. It took me quite a few weeks of noticing it, being puzzle...

Seems like it's not fixed yet, it's only 2 months old so if you inquire with Damus they might fix it and include it in the next release. I know it's this issue because it's indicated here: Failed to decode NWC Wallet response JSON. Error: typeMismatch(damus.WalletConnect.Response.Result.ResultType, Swift.DecodingError.Context(codingPath: [], debugDescription: "result_type get_info is unknown", underlyingError: nil))

Separate topic. But why does about 80% of the time zaps fail to users using primal wallets.

Is this a Damus issue or a Rizful issue? If it’s Rizful, can u please try to zap from yakihonne and if there is a user who u consistently cannot zap, would you please provide the profile link to this user here? Thanks.

Not damus. I m on amethyst. 8 of 10 times zapping a note of a primal user fails. For example @profk notes.

Error message

Thanks. This looks to be specific to some kind of interaction between Amythest and Primal.. you can see it is failing at the "callback" stage of the zap, which is before Rizful gets involved... also, I just tried zapping @profk from Yakihonne and Jumble.social on the web, and it succeeded both times... this also points to some kind of Amythest/Primal Wallet issue.

Forking off convo again… Zaps in/out working via @Damus only (using @Rizful.com set up above) Tested on Damus, YakiHonne (web+iOS) and Primal (web+iOS). Wallet is not connected on latter two - do wallets need to be manually connecting to each client/app? Previous @YakiHonne wallet receives zaps yet won’t send out. Tried zapping posts, profiles, LN address + LN invoice (there are a few unretrievable sats in there ATM) tam@wallet.yakihonne.com Previous to that I was using the primal app and this issue came about when shifting from their wallet. Previous to using Primal app, Damus and YakiHonne were zapping flawlessly (via WoS). No idea if any is correlated.

I read this message twice and I think understand about 20% of what you wrote. if you have any specific test cases that involve Rizful and that are failing, if you could lay them out in extreme detail, like exactly what steps you take to reach the failure, then we would like to try to reproduce them.

These might be helpful.

Using Rizful.com | Megalith Lightning Docs

Rizful is an easy way to send & receive Lightning payments, either through the web, or via Nostr Wallet Connect.

😂 Zapping function only works via Damus, not other clients (using Rizful). Yesterday, I moved to Rizful wallet from YakiHonne wallet (because I could receive sats but not send them). 5ish days ago I moved to YakiHonne wallet from Primal wallet (because I found out Primal is not what I believe nostr to be). Not sure it’s a rizful issue. Perhaps, it’s a skill issue. TL;DR I can’t get the zapping function to work across clients

@Vitor Pamplona @Amethyst

"can’t get the zapping function to work across clients" -- just to be clear, each client needs to be set up separately with an NWC string.. so u could follow the relevant tutorial for each client...

Using Rizful.com | Megalith Lightning Docs

Rizful is an easy way to send & receive Lightning payments, either through the web, or via Nostr Wallet Connect.

Can't wait to see what happens in 5 days form now lol

Http status code 426? That's weird. @miljan do you guys force some http version in the wallet?

😛😂 Spoiler: 🦗🦗🦗 Poor devs for reading nondev skillissues. Core irritant was primal is fuck all and offramping that app gave me 5ish days internet ick. 🤓😃

Is the issue solved for you or still facing it ?