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

Android 30+: unable to load TLS credentials error. #5886

Closed
kaganovych opened this issue Oct 24, 2021 · 3 comments
Closed

Android 30+: unable to load TLS credentials error. #5886

kaganovych opened this issue Oct 24, 2021 · 3 comments

Comments

@kaganovych
Copy link
Contributor

kaganovych commented Oct 24, 2021

Background

Hey. I was able to build the AAR file for Android. But there's a common issue with Android 30+ inclusively. When I try to connect to Lndmobile with this lines:

Lndmobile.start(
                """--bitcoin.active
                        --lnddir="${file.path}"
                        --bitcoin.node=neutrino 
                        --bitcoin.testnet 
                        --no-macaroons""".trimIndent(),
                StartCallback()
            )

it tells me next:

[WRN] LTND: open /data/user/0/com.bitmynt/files/lnd/lnd.conf: no such file or directory
[INF] LTND: Version: 0.13.99-beta commit=healthcheck/v1.2.0-1-gcac8da81, build=development, logging=default, debuglevel=info
[INF] LTND: Active chain: Bitcoin (network=testnet)
[INF] RPCS: Generating TLS certificates...
[ERR] LTND: unable to load TLS credentials: route ip+net: netlinkrib: permission denied
[INF] LTND: Shutdown complete

Your environment

  • version of lnd - master or v0.13.99-beta
  • which operating system - MacOS Big Sur 11.5.2

Steps to reproduce

Try to connect to Lndmobile on Android 30 or above.

Expected behaviour

Client is connected successfully.

Actual behaviour

An error appeared with TLS.

Thanks in advance for helping!

@guggero
Copy link
Collaborator

guggero commented Oct 25, 2021

This seems to be a known problem with the Android API: golang/go#40569.
Can you try if adding the --tlsdisableautofill flag fixes the problem for you?

@kaganovych
Copy link
Contributor Author

Thanks, this command helped!

@guggero
Copy link
Collaborator

guggero commented Oct 25, 2021

Thanks, this command helped!

Closing as this seems to be resolved. Feel free to re-open if you run into other issues around TLS and Android.

@guggero guggero closed this as completed Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants