Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Stuck on loading after connecting to local node (incompatible with latest lnd master branch) #1320

Closed
cherijs opened this issue Jan 13, 2019 · 21 comments
Closed

Stuck on loading after connecting to local node (incompatible with latest lnd master branch) #1320

cherijs opened this issue Jan 13, 2019 · 21 comments
Assignees
@mrfelton
Labels
scope: onboarding issues relating to the onboarding process type: bug 🐛 Something isn't working
Milestone
v0.3.4-beta

Comments

@cherijs
Copy link

cherijs commented Jan 13, 2019 •
edited
Loading

Stuck on loading after connecting to local testnet node (localhost:10009)

checkPropTypes.js:19 Warning: Failed prop type: The prop network is marked as required in Network, but its value is undefined.

image

stateProps.info.network is empty object
@mrfelton
Copy link
Member

@cherijs can you provide exact steps to replicate please? Thanks.

@mrfelton mrfelton added type: bug 🐛 Something isn't working scope: onboarding issues relating to the onboarding process labels Jan 13, 2019
@johnfigs
Copy link

johnfigs commented Jan 14, 2019 •
edited
Loading

This is also happening to me. I installed zap via the .deb package on Ubuntu 18.04 LTS. Added the localhost:port, tls.cert, macaroon path and the continuous loading screen. Quitting the app and re-opening yields the same loading screen. Let me know what other information you may need such as logs. I have included errors thrown when running "zap-desktop"

user@Computer:~$ zap-desktop (node:17600) ExperimentalWarning: The http2 module is an experimental API. Unhandled rejection Error: ENOENT: no such file or directory, open '/opt/ZapDesktop/resources/app-update.yml' at readFile (/opt/ZapDesktop/resources/app.asar/webpack:/node_modules/electron-updater/out/AppUpdater.js:625:1) at Generator.next (<anonymous>) From previous event: at t.AppImageUpdater.loadUpdateConfig (/opt/ZapDesktop/resources/app.asar/webpack:/node_modules/electron-updater/out/AppUpdater.js:620:1) at t.Lazy.loadUpdateConfig (/opt/ZapDesktop/resources/app.asar/webpack:/node_modules/electron-updater/out/AppUpdater.js:221:1) at t.Lazy.creator [as value] (/opt/ZapDesktop/resources/app.asar/webpack:/node_modules/lazy-val/out/main.js:17:1) at value (/opt/ZapDesktop/resources/app.asar/webpack:/node_modules/electron-updater/out/AppUpdater.js:503:1) at Generator.next (<anonymous>) at runCallback (timers.js:696:18) at tryOnImmediate (timers.js:667:5) at processImmediate (timers.js:649:5) From previous event: at t.AppImageUpdater.getUpdateInfoAndProvider (/opt/ZapDesktop/resources/app.asar/webpack:/node_modules/electron-updater/out/AppUpdater.js:499:1) at getUpdateInfoAndProvider (/opt/ZapDesktop/resources/app.asar/webpack:/node_modules/electron-updater/out/AppUpdater.js:532:1)

@mrfelton
Copy link
Member

This sounds like a case of #1310 or #1173

These issues are resolved in master and will be fixed in the next release, but you can resolve manually by following the steps here:

#1173 (comment)

@cherijs
Copy link
Author

cherijs commented Jan 14, 2019

This sounds like a case of #1310 or #1173

These issues are resolved in master and will be fixed in the next release, but you can resolve manually by following the steps here:

#1173 (comment)

image

Ok, after " Launch Now" same loading screen

@mrfelton
Copy link
Member

@cherijs could you explain your setup a little please? You have your own instance of LND running on your local machine that you are trying to connect to using the "Connect to your own node" option?

Can you provide exact steps to reproduce please? Thanks

@johnfigs
Copy link

johnfigs commented Jan 14, 2019 •
edited
Loading

@mrfelton After the fix, as @cherijs stated. The loading screen comes up again. To answer the question you posed. I am running bitcoind, and my own LND on my local machine and I am attempting to "connect to your own node". Also, @mrfelton should I start my own issue? I don't want to hijack this thread, just thought it was prudent to show that > 1 user was having this issue.

@cherijs
Copy link
Author

cherijs commented Jan 14, 2019

@cherijs could you explain your setup a little please? You have your own instance of LND running on your local machine that you are trying to connect to using the "Connect to your own node" option?

Can you provide exact steps to reproduce please? Thanks

Exactly, LND running on local machine - and i'm trying to connect through "Connect to your own node"

image

Alter opening app, LND console prints

image

@mrfelton
Copy link
Member

mrfelton commented Jan 14, 2019 •
edited
Loading

Ok, so based on those logs @cherijs I believe your issue to be this one - #1235 - which is also fixed in the master branch. Unfortunately, there is no way to resolve this manually in 0.3.2.

We are aiming to push 0.3.3 in the coming days.

It would be great if you could checkout the master branch and run the development version of the wallet to verify that the issue has indeed been resolved. You can find some notes on how to do this here https://github.com/LN-Zap/zap-desktop/blob/master/ADVANCED.md

@cherijs
Copy link
Author

cherijs commented Jan 14, 2019

same :(

Image

@cherijs
Copy link
Author

cherijs commented Jan 14, 2019

lnd version 0.5.1-beta commit=v0.5.1-beta-343-g55b580f2b80d2e62af4067d3ddf8688614bf0914
Bitcoin Core Daemon version v0.17.99.0-3ec4cc0a9

@mrfelton
Copy link
Member

@cherijs - could you join our slack and ping me there? Might be easier to walk through this with you in real time than going back and forth on this issue.

@mrfelton mrfelton self-assigned this Jan 14, 2019
@mrfelton mrfelton added this to the v0.3.3-beta milestone Jan 14, 2019
@mrfelton
Copy link
Member

@cherijs the issue here appears to be an incompatibility with the latest development version of lnd. Amongst other things, the result from lncli getinfo has changed as per lightningnetwork/lnd#2399

You will need to install lnd 0.5.1 to use Zap currently as we are not tracking lnd HEAD right now.

@mrfelton mrfelton modified the milestones: v0.3.3-beta, v0.4.0-beta Jan 14, 2019
@mrfelton mrfelton changed the title Stuck on loading after connecting to local node Stuck on loading after connecting to local node (incompatible with latest lnd master branch) Jan 14, 2019
@johnfigs
Copy link

@mrfelton isn't @cherijs already using 0.5.1? He stated this was his LND version a couple comments up.

@mrfelton
Copy link
Member

@Jfigs101 he is using the most recent checkout of lnd from the master branch - I confirm with him via slack.

@mrfelton
Copy link
Member

lnd version 0.5.1-beta commit=v0.5.1-beta-343-g55b580f2b80d2e62af4067d3ddf8688614bf0914

This is 343 additional commits on top of 0.5.1

@mrfelton mrfelton mentioned this issue Jan 17, 2019
Closed
@ghost ghost mentioned this issue Jan 20, 2019
Closed
@mrfelton mrfelton modified the milestones: v0.4.0-beta, v0.3.4-beta Jan 25, 2019
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 26, 2019
@mrfelton
fix(lnd): support multiple lnd versions
b03e9cc 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 26, 2019
@mrfelton
fix(lnd): support multiple lnd versions
6e644d5 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 28, 2019
@mrfelton
fix(lnd): support multiple lnd versions
abf3a0e 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 29, 2019
@mrfelton
fix(lnd): support multiple lnd versions
4a5f59d 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 29, 2019
@mrfelton
fix(lnd): support multiple lnd versions
20875de 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
@mrfelton mrfelton mentioned this issue Jan 30, 2019
Closed
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 31, 2019
@mrfelton
fix(lnd): support multiple lnd versions
4510e5d 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
@mariodian
Copy link

Have the same issue on the latest lnd.

mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 31, 2019
@mrfelton
fix(lnd): support multiple lnd versions
1fd4660 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 31, 2019
@mrfelton
fix(lnd): support multiple lnd versions
6b053ae 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue Jan 31, 2019
@mrfelton
fix(lnd): support multiple lnd versions
3e68dab 
Store multiple rpc.proto files and select the most appropriate one based
on the version of lnd that we are connecting to. Adapt api calls as
needed in order or support backwards incompatible changes in lnd.

Fix LN-Zap#1320
@mrfelton
Copy link
Member

@mariodian you can try the patch in #1431 if you like, which should resolve the issue. Alternatively, we will be making a new release soon that will include the fix.

@mariodian
Copy link

@mrfelton does it work with a remote lnd too?

@mrfelton
Copy link
Member

mrfelton commented Feb 1, 2019

Yes @mariodian

@stevedekorte
Copy link

I'm seeing this on Zap Version 0.3.1-beta (0.3.1-beta.5049).

@bolatovumar
Copy link
Contributor

@stevedekorte the latest version 0.6.2-beta. You should upgrade as 0.3.1-beta is very old.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mrfelton mrfelton

Labels
scope: onboarding issues relating to the onboarding process type: bug 🐛 Something isn't working
Projects
None yet
Milestone
v0.3.4-beta
Development

No branches or pull requests
6 participants
@stevedekorte @mrfelton @bolatovumar @cherijs @mariodian @johnfigs