background-geolocation-console: New version not getting locations

Hello,

So I was using an oldest version of the console and was fine. Today I made an update and suddenly looks like the locations are not properly inserted. Any idea of what happened here?

Here’s what i get when I get the location. It says Authorization: undefined…maybe it’s caused by that?

POST /locations { “host”: “live.itineralia.es:8080”, “content-type”: “application/json”, “connection”: “keep-alive”, “accept”: “/”, “user-agent”: “Mobility%20City/1.4.2 CFNetwork/887 Darwin/17.0.0”, “content-length”: “430”, “accept-language”: “en-us”, “accept-encoding”: “gzip, deflate” } Authorization: undefined { “location”: { “coords”: { “speed”: 25.35, “longitude”: -122.40558808, “floor”: 0, “latitude”: 37.74389497, “accuracy”: 5, “altitude_accuracy”: -1, “altitude”: 0, “heading”: 31.29 }, “extras”: {}, “is_moving”: true, “odometer”: 304.6, “uuid”: “26348E08-8D1E-4FA0-86BA-49BA68F5540C”, “activity”: { “type”: “unknown”, “confidence”: 100 }, “battery”: { “level”: -1, “is_charging”: false }, “timestamp”: “2017-11-22T18:03:04.045Z” } }

Executing (default): INSERT INTO locations (id,company_token,uuid,device_model,latitude,longitude,accuracy,altitude,speed,heading,odometer,activity_type,activity_confidence,battery_level,battery_is_charging,is_moving,geofence,provider,extras,recorded_at,created_at) VALUES (NULL,NULL,‘26348E08-8D1E-4FA0-86BA-49BA68F5540C’,‘UNKNOWN’,37.74389497,-122.40558808,5,0,25.35,31.29,304.6,‘unknown’,100,-1,0,1,NULL,NULL,‘{}’,‘2017-11-22 18:03:04.045 +00:00’,‘2017-11-22 18:03:04.093 +00:00’);

PS - When I mean older and newer version i talk about those versions. See attached screenshots.

Thanks!

captura de pantalla 2017-11-22 a las 19 03 05 captura de pantalla 2017-11-22 a las 19 03 53

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 24 (13 by maintainers)

Commits related to this issue

Most upvoted comments

Also wrt privacy, you have the option to delete your own data in the web app. That really does do a DELETE FROM locations, as can be seen in the source code.

Location data of a single device or even hundreds of devices spread all over the world isn’t particularly interesting to anyone. It’s only when aggregating many thousands of devices within a small, targeted geographical area that the data would become useful to anyone.

You can spin up your own server if you wish or use my public server. Posting to a server available on the internet allows you to post in the field while you’re away from localhost.

You can easily host the console on own your instance.

What’s my privacy policy? I’m not interested at all with your location data outside of the context of a particular issue you might have. Posting to my server gives me the chance to observe your exact data instead of looking at screenshots. Your data is going to be deleted from my database after a time (eg 3 months).

This is development / field-testing service for developers only. Obviously you’re not going to use this in production.

My public server is primarily designed for new users to quickly boot the SampleApp and see immediate results.