pull down to refresh

Hey @k00b I tried to set my desired wallet balance back to zero to test if I had gotten myself out of whatever NWC prison I was in and I got the following error message:
Cannot read properties of undefined (reading 'includes')
20 sats \ 1 reply \ @k00b 19 Sep
hmmmm @ek does this sound familiar?
reply
20 sats \ 0 replies \ @ek 19 Sep
No but it could be caused if the get_info response doesn't actually contain methods since that's one example where we call includes in the given context:
{ "result_type": "get_info", "result": { "alias": "string", "color": "hex string", "pubkey": "hex string", "network": "string", // mainnet, testnet, signet, or regtest "block_height": 1, "block_hash": "hex string", "methods": ["pay_invoice", "get_balance", "make_invoice", "lookup_invoice", "list_transactions", "get_info"], // list of supported methods for this connection } }
But that would be a weird error, why would that suddenly happen for an existing connection.
reply
20 sats \ 4 replies \ @ek 19 Sep
You got this message by only changing the withdraw threshold ("desired balance")?
reply
Yes. I had it at zero yesterday but zaps were not going through because I reached some rate limit with coinos on my NWC so I switched it to 2500 sats yesterday so that I could zap. I wanted to test if my rate limit issue was resolved today and if I had just been given at time out or if it was something that persisted so I switched the desired balance back to 0 and got that error message when I tried to save.
Maybe because of my rate limit issue I need to delete the connection and attach again?
reply
0 sats \ 2 replies \ @ek 19 Sep
Ohh, a rate limit causing this makes a lot of sense! But that means their error response is not in the standardised format we expect. Will look into that, thank you!
reply
Should I detach the wallet and then attach again as a means of getting around rate limit issue?
reply
0 sats \ 0 replies \ @ek 19 Sep
No, I don’t think that will help
reply