cordova-plugin-background-geolocation: NullPointerException: onTaskRemoved (LocationService.java:199)

Exception reported on google play. No feedback from the user unfortunately. If I manage to reproduce it or get more info I’ll update the issue.

Your Environment

  • Plugin version: 2.2.5
  • Platform: Android
  • OS version: 5.0.2
  • Device manufacturer and model: Sony C6916
  • Cordova version (cordova -v): 6.4.0
  • Cordova platform version (cordova platform ls): 6.0.0
  • Plugin configuration options:
  • Link to your project:

Debug logs

Exception java.lang.RuntimeException: Unable to start service com.marianhello.bgloc.LocationService@3fef4865 with Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 }: java.lang.NullPointerException: Attempt to invoke virtual method ‘java.lang.Boolean com.marianhello.bgloc.Config.getStopOnTerminate()’ on a null object reference

Caused by java.lang.NullPointerException: Attempt to invoke virtual method ‘java.lang.Boolean com.marianhello.bgloc.Config.getStopOnTerminate()’ on a null object reference com.marianhello.bgloc.LocationService.onTaskRemoved (LocationService.java:199) android.app.ActivityThread.handleServiceArgs (ActivityThread.java:2920) android.app.ActivityThread.access$2100 (ActivityThread.java:149) android.app.ActivityThread$H.handleMessage (ActivityThread.java:1422) android.os.Handler.dispatchMessage (Handler.java:102) android.os.Looper.loop (Looper.java:211) android.app.ActivityThread.main (ActivityThread.java:5317) java.lang.reflect.Method.invoke (Method.java) java.lang.reflect.Method.invoke (Method.java:372) com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1016) com.android.internal.os.ZygoteInit.main (ZygoteInit.java:811)

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 26 (15 by maintainers)

Commits related to this issue

Most upvoted comments

ok. can you please try cordova-plugin-mauron85-background-geolocation@3.0.0-alpha.17?

Notice: this issue has been closed because it has been reported for branch 2.x or later. It could be already fixed in v3 or is not relevant anymore. You may reopen this issue if it has been closed in error.