#[3] got it to work just fine with WoS LNURL and ln address so currently I’ve only had problems with #[4] ln address and lnurl. I’ll look more into this tomorrow and see if I can help out with a PR.
Discussion
problems? can I help? what did you encounter?
When I use my Alby ln address 0xtr@oxtr.dev, the site just goes blank and a very generic react-dom error is printed to the console. This also happens to alby lnurls. Seems to work just fine with both WoS ln addresses and lnurls however.
that sounds strange. can I see the code? or test it somehow.
it’s all the lnurl spec, so there should not be ang difference.
Seems like the problem is that the website doesn’t support LUD-18.
When looping over the payerData key in the response from Alby, we error because we try to render the entire payerData object which apparently React doesn’t like. This is where the error essentially occurs:
https://github.com/andrerfneves/lightning-decoder/blob/master/src/app.js#L478
When I build a special handling if-block for the “payerData” key, it renders perfectly fine. I’ll try to find a way to display this data and make a PR for it.