bumi -- 326d can I test it and see the code somewhere? I think the prompts actually should only get closed on success. 🤔 replycan I test it and see the code somewhere? I think the prompts actually should only get closed on success. 🤔
thread · root 6e42ef5c…84ed · depth 4 · · selected 5d764c44…2ae5
thread
root 6e42ef5c…84ed · depth 4 · · selected 5d764c44…2ae5
Unfortunately, we’ve needed to add a note to our Bitcoin checkout that Alby extension does not work. We’ve triedgetting in touch with their support, but they’ve been unresponsive on assisting with why they’re the onlyincompatible extension. We apologize to any customers who use Alby. Please use a different extension topurchase/renew.https://file.nostrmedia.com/p/3ca6d7c20e530e7561eb29a066dfa9876e791f411b52187da7b314dc48d588ce/84770936790b7f933ac294c4f11546149249a59f4c204eb4f21dcf96f696615d.jpg
what's not working? and how did you reach out?
Hey! Had sent an email to support. Initially got a reply. Then tried sending multiple follow-up replies, butreceived no further response. The issue is that once you use the Alby extension to sign using Nostr account andissue payment from wallet, it must interact with the DOM and prematurely closes the payment modal, which islistening for successful payment. Due to Alby closing the modal, the payment goes through, but not ourserver-side checks to add folk’s accounts. I had offered to give Alby support a coupon code that’d wave any feeto help test as the Alby extension service worker logs showed no errors, nor did anything on our end in browserdev console or server logs. So, we’ve been a bit stumped by why Alby extension force-closes the modal atpayment. Thanks!
can I test it and see the code somewhere?I think the prompts actually should only get closed on success. 🤔
d49a9023…a8df -- 327d [parent] | reply [1 reply]Hey! Had sent an email to support. Initially got a reply. Then tried sending multiple follow-up replies, but received no further response. The issue is that once you use the Alby extension to sign using Nostr account and issue payment from wallet, it must interact with the DOM and prematurely closes the payment modal, which is listening for successful payment. Due to Alby closing the modal, the payment goes through, but not our server-side checks to add folk’s accounts. I had offered to give Alby support a coupon code that’d wave any fee to help test as the Alby extension service worker logs showed no errors, nor did anything on our end in browser dev console or server logs. So, we’ve been a bit stumped by why Alby extension force-closes the modal at payment. Thanks!