-
Notifications
You must be signed in to change notification settings - Fork 27
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
Request to add release 0.0.6 to Ledger Live #27
Comments
+1 would appreciate that or at least a build guide. I struggled to build it and had many errors which I managed to ignore by modifying a bit the Makefile. I have now the app loaded with v0.0.6 however I'm getting the message "This app is not genuine" is there a way to get rid of it ? |
Hi,
Did you get it to work? Could you share the make options? Thanks
…On Thu, Jun 25, 2020, 12:41 AM Chakib Benziane ***@***.***> wrote:
+1 would appreciate that or at least a build guide.
I struggled to build it and had many errors which I managed to ignore by
modifying a bit the Makefile.
I have now the app loaded with v0.0.6 however I'm getting the message
"This app is not genuine" is there a way to get rid of it ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVKHO43I5RKEDGB6XZO54TRYI3DVANCNFSM4OFNUUWQ>
.
|
I used a fresh latest ubuntu docker image, installed clang-6.0, libc6-dev-i386 and build-essentials. I did not use BLOS_ENV only BOLOS_SDK. I change the following on the Makefile:
|
And it works with these options? what about the command for |
Yes it works and should load without problems using the Using it on the ledger I did not notice anything broken yet other than the "Non genuine" message appearing everytime I launch the app. |
Due #25, the latest Ledger Live release is 0.0.7, this issue can probably be closed. |
Current release is 0.0.6 but Ledger Live is 0.0.5, even with latest firmware on Nano S. Likely related to #25
The text was updated successfully, but these errors were encountered: