You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we got the error "Attempt to invoke virtual method 'java.lang.String com.transistorsoft.locationmanager.geofence.TSGeofence.getIdentifier()' on a null object reference"
Stack trace:
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.transistorsoft.locationmanager.geofence.TSGeofence.getIdentifier()' on a null object reference
at com.transistorsoft.locationmanager.geofence.TSGeofenceManager.startMonitoringPolygon
at com.transistorsoft.locationmanager.geofence.TSGeofenceManager.start
at com.transistorsoft.locationmanager.service.TrackingService.start
at com.transistorsoft.locationmanager.adapter.BackgroundGeolocation$z0.run
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
We have tried to investigate this issue on our end. We tried to add corrupted/invalid/empty/undefined/null... geofences in BackgroundGeolocation.addGeofences method, but we were not able to reproduce this error in debug build.
Could you please look at this in the native code? We would really appreciate it. Or what do you suggest to do on our end? Do you have some idea?
App is not crashing after startMonitoringPolygone is called
Actual Behavior
App is crashing on some devices after startMonitoringPolygone is called
Steps to Reproduce
Add some valid geofences to BackgroundGeolocation.addGeofences(geofences)
Start monitore polygone
App crash
Context
We have tried to investigate this issue on our end. We tried to add corrupted/invalid/empty/undefined/null... geofences in BackgroundGeolocation.addGeofences method, but we were not able to reproduce this error in debug build.
Our geofences look like this:
It seems that a Geofence has been removed from the database but the plugin still contains a reference to its identifier in a list of monitoredPolygons.
Hello Chris,
we got the error "Attempt to invoke virtual method 'java.lang.String com.transistorsoft.locationmanager.geofence.TSGeofence.getIdentifier()' on a null object reference"
Stack trace:
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.transistorsoft.locationmanager.geofence.TSGeofence.getIdentifier()' on a null object reference
at com.transistorsoft.locationmanager.geofence.TSGeofenceManager.startMonitoringPolygon
at com.transistorsoft.locationmanager.geofence.TSGeofenceManager.start
at com.transistorsoft.locationmanager.service.TrackingService.start
at com.transistorsoft.locationmanager.adapter.BackgroundGeolocation$z0.run
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
We have tried to investigate this issue on our end. We tried to add corrupted/invalid/empty/undefined/null... geofences in BackgroundGeolocation.addGeofences method, but we were not able to reproduce this error in debug build.
Could you please look at this in the native code? We would really appreciate it. Or what do you suggest to do on our end? Do you have some idea?
Your Environment
react-native -v
): 0.73.7Expected Behavior
App is not crashing after startMonitoringPolygone is called
Actual Behavior
App is crashing on some devices after startMonitoringPolygone is called
Steps to Reproduce
Context
We have tried to investigate this issue on our end. We tried to add corrupted/invalid/empty/undefined/null... geofences in BackgroundGeolocation.addGeofences method, but we were not able to reproduce this error in debug build.
Our geofences look like this:
Debug logs
Logs
The text was updated successfully, but these errors were encountered: