Skip to content
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

Release v0.1.5-alpha on Mac not functional #245

pors opened this issue Mar 18, 2018 · 2 comments

Release v0.1.5-alpha on Mac not functional #245

pors opened this issue Mar 18, 2018 · 2 comments


Copy link

@pors pors commented Mar 18, 2018


Downloading and running the Mac binary results in a forever syncing app.

Steps to reproduce the behavior

Download app here:
Move app to /Applications folder
Run the app

Expected behavior

After a while, the syncing should be finished

Actual behavior

Syncing never finishes, may errors in the log

Screenshot and/or logs if applicable

Logs here: (requires access to the lightningcommunity slack.

@pors pors changed the title Release v0.1.5-alpha on Mac not fuctional Release v0.1.5-alpha on Mac not functional Mar 18, 2018
@tanx tanx added the v0.1 label Mar 20, 2018
Copy link

@PJUllrich PJUllrich commented Jul 5, 2018

I don't have access to the logs, but I experience the same issue with the 0.2.0-prealpha version. The logs indicate that the app has fully caught up with the chain (the latest block height in the logs is equal to the latest block height on e.g. Blockexplorer). However, I get the warning

[info] /Applications/ 2018-07-05 11:44:36.791 [WRN] BTCN: Somehow we have 0 cfheaders for block 1 (00000000b873e79784647a6c82962c70d228557d24a747ea4d1b8bbe878e1206)

I think that this might be the problem. The chain is synced, but maybe not validated since the cfheaders for block 1 are missing?

Copy link

@tanx tanx commented Jul 5, 2018

@PJUllrich yes I created a new issue for prerelease. Closing in favor of #433

@tanx tanx closed this Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants