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

TLS handshake error when POSTing location changes #570

PhillippOhlandt opened this Issue Apr 8, 2019 · 0 comments


None yet
1 participant
Copy link

PhillippOhlandt commented Apr 8, 2019

Your Environment

  • Plugin version: 3.0.1
  • Platform: Android
  • OS version: 9
  • Device manufacturer and model: Oneplus 6
  • Running in Simulator:
  • Cordova version (cordova -v): 9.0.0
  • Cordova platform version (cordova platform ls): 8.0.0
  • Plugin configuration options:
  • Link to your project:


My local development API runs over HTTPS. I imported the CA cert for my local certificate on my phone so that Chrome and the Cordova JS app properly communicate with the API. (Chrome marks the page as trusted and the app has no problems sending requests)

Expected Behavior

The background POST request should properly communicate with the API because the CA cert is installed on the Android device.

Actual Behavior

I cannot really debug the outgoing request (as it doesn't show up on the chrome devtools, because it comes from native code) but I get the following in the log of my backend service.

23:46:19 app         | 2019/04/08 23:46:19 http: TLS handshake error from remote error: tls: unknown certificate

Possible Fix

Maybe I just miss some additional configuration for it to work?

Steps to Reproduce

You basically just need a backend service with a self signed cert which was also signed by an own CA cert. The CA cert should be installed on the Android device. Then let the plugin POST to it.


It hopefully doesn't affect the production built because that will use the real backend with a proper certificate. But right now I am not able to test it on my development machine and the real infrastructure is not in place yet.

Debug logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.