Location share sent the wrong location.

[ara4n]

Steps to reproduce

1. @daniellekirkwood sent me a static location
2. i went to it
3. it turned out to be about 500m from where she actually was.

Outcome

What did you expect?

I'm assuming the problem is that either:

• She'd not given the app permission for accurate location sharing, so it was defaulting to the nearest cell tower rather than using actual GPS?
• She didn't wait for GPS to get a lock, and failed to spot the big radius of uncertainty around her pin
• The app should have waited for GPS to warm up and stabilise before letting her send the pin

What happened instead?

I missed a meeting and overheated while trekking around London.

Your phone model

unsure

Operating system version

26.5

Application version

26.07.1 (234)

Homeserver

one.ems.host

Will you send logs?

Yes

[utop-top]

There are also issues with real-time location sharing; it simply doesn't move as the location changes.

[Velin92]

We would need to know the current permissions setup on their device to know for sure if this is an app issue or an OS settings issue. Can we get a screenshot of the current permissions given to the app? From the logs it looks alright.

[Velin92]

There are also issues with real-time location sharing; it simply doesn't move as the location changes.

About this, we only send updates if the movement is of about 10 meters, and only every 3 seconds, however you can change this setting in the Advanced Settings section of the app, and send updates with just 1 meter of movement. This is done to avoid consuming excessive amounts of battery when sending Live Location updates

[utop-top]

That’s not the reason; the real-time location updates only trigger a single movement, after which it stops updating entirely, no matter how many meters you move.

[github-actions]

This issue has been awaiting further information for the past 30 days so will now be marked as stale. Please provide the requested information within the next 7 days to keep it open.