-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] (Account is still loading) message always when I switch from my LND-LNC account to Alby account #2275
Comments
hi can i please be assigned this issue? |
Thanks for being willing to work on this issue. Are you able to reproduce it locally following bitcoinuser's instructions? |
i'm still on it but i havent reproduced it yet? |
I couldnt reproduce this because while switching from the lnd node to alby itself, an error message occurs |
@Ladyperpetua what error do you get? |
alby.video.mp4 |
an issue #2305 was created on the lnd node creation. i couldn't create the lnd-lnc because i needed a pairing phrase and i was lost on where and how to get one |
@Ladyperpetua was the connection working previously? where is your LND node connected to? https://lnd1.regtest.getalby.com? https://github.com/getAlby/lightning-browser-extension/wiki/Test-setup |
@Ladyperpetua oh, I see. You will probably need to run your own node to reproduce this. I think you should be able to reproduce it before working on the task. |
Yes, my connection was fine, I tried other alternative using a different browser, and i created an eclair node through polar. THE LND node just wasn't working |
I will create my own node and get back to you if i come across any issue |
I also wanted to ask if i could work on it without getting assigned? |
@Ladyperpetua sure, that's fine. |
Describe the bug
(Account is still loading) message always when I switch from my LND-LNC account to Alby account.
document_4972210748689220298.mp4
Steps To Reproduce
Expected behavior
No Account is still loading message.
Alby information
Alby: 1.28.1
The text was updated successfully, but these errors were encountered: