FindMy map icon locations won't update

[jwprescod]

The location information is accurate but the icons on maps for friends and items/devices won't update for at least a couple days in my experience. Issue brought up on discord, screenshot attached below

[SpaceSaver]

Coordinates probably aren't accurate but match where it's displayed on the map.

[jwprescod]

That's not the case. For instance, in this picture, the one highlighted is in Toronto - which is shown in the information section. But on the map itself, the person is still at their house, 60km away. And in most instances the map (not the information, but the map) will stay stagnant for days for both friends and devices.

[SpaceSaver]

But, are the latitude and longitude also incorrect?

[jwprescod]

They are also incorrect

[SpaceSaver]

They are also incorrect

I have the same issue

[zlshames]

So, sometimes Apple's update function will give us a new address, but not new coordinates. It also could just be a caching issue. One way to check would be the following:

Use your browser and go to https://{your server url}/api/v1/findmy/friends?password={your password}

You will get a JSON response. Find the friend that is showing incorrectly (by the handle). Put the coordinates it has for them into Google maps. Does it match the address? Does it match what shows in the BlueBubbles app? If it matches BB, then it could be a quirk of how apple sends updates that we need to fix in the private API helper/server. If it doesn't match BB, then it may be a caching issue on the client

[SpaceSaver]

@zlshames Restarting Messages from the server settings page on the client updates the coordinates.

[zlshames]

@zlshames Restarting Messages from the server settings page on the client updates the coordinates.

Is it reproducible? Like if this happens, does restarting Messages fix it always? Also, instead of restarting, what if you just reopened iMessage, aka brought it into focus? Does it also fix it?

[jwprescod]

@zlshames Restarting Messages from the server settings page on the client updates the coordinates.

Is it reproducible? Like if this happens, does restarting Messages fix it always? Also, instead of restarting, what if you just reopened iMessage, aka brought it into focus? Does it also fix it?

Didn't mean to close the thread lol, but I just tried restarting Messages from the server settings page, and the coordinates were updated for me too fwiw.

I have also been typing in that findmy/friends URL with my server name and password and I get "Not Found"

[SpaceSaver]

@zlshames Restarting Messages from the server settings page on the client updates the coordinates.

Is it reproducible? Like if this happens, does restarting Messages fix it always? Also, instead of restarting, what if you just reopened iMessage, aka brought it into focus? Does it also fix it?

Didn't mean to close the thread lol, but I just tried restarting Messages from the server settings page, and the coordinates were updated for me fwiw.

I have also been typing in that findmy/friends URL with my server name and password and I get "Not Found"

The URL was supposed to be https://{your server url}/api/v1/icloud/findmy/friends?password={your password}

[Abolfazl]

So, sometimes Apple's update function will give us a new address, but not new coordinates. It also could just be a caching issue. One way to check would be the following:

Use your browser and go to https://{your server url}/api/v1/findmy/friends?password={your password}

You will get a JSON response. Find the friend that is showing incorrectly (by the handle). Put the coordinates it has for them into Google maps. Does it match the address? Does it match what shows in the BlueBubbles app? If it matches BB, then it could be a quirk of how apple sends updates that we need to fix in the private API helper/server. If it doesn't match BB, then it may be a caching issue on the client

For me when this issue comes up, it is the latter where the address does not match the coordinates.

[zlshames]

So, sometimes Apple's update function will give us a new address, but not new coordinates. It also could just be a caching issue. One way to check would be the following: Use your browser and go to https://{your server url}/api/v1/findmy/friends?password={your password} You will get a JSON response. Find the friend that is showing incorrectly (by the handle). Put the coordinates it has for them into Google maps. Does it match the address? Does it match what shows in the BlueBubbles app? If it matches BB, then it could be a quirk of how apple sends updates that we need to fix in the private API helper/server. If it doesn't match BB, then it may be a caching issue on the client

For me when this issue comes up, it is the latter where the address does not match the coordinates.

Do you know what's more updated tho? Like what's more accurate at the current checking time?

[Abolfazl]

So, sometimes Apple's update function will give us a new address, but not new coordinates. It also could just be a caching issue. One way to check would be the following: Use your browser and go to https://{your server url}/api/v1/findmy/friends?password={your password} You will get a JSON response. Find the friend that is showing incorrectly (by the handle). Put the coordinates it has for them into Google maps. Does it match the address? Does it match what shows in the BlueBubbles app? If it matches BB, then it could be a quirk of how apple sends updates that we need to fix in the private API helper/server. If it doesn't match BB, then it may be a caching issue on the client

For me when this issue comes up, it is the latter where the address does not match the coordinates.

Do you know what's more updated tho? Like what's more accurate at the current checking time?

The long address field is accurate but the coordinates do not update

[jwprescod]

So, sometimes Apple's update function will give us a new address, but not new coordinates. It also could just be a caching issue. One way to check would be the following: Use your browser and go to https://{your server url}/api/v1/findmy/friends?password={your password} You will get a JSON response. Find the friend that is showing incorrectly (by the handle). Put the coordinates it has for them into Google maps. Does it match the address? Does it match what shows in the BlueBubbles app? If it matches BB, then it could be a quirk of how apple sends updates that we need to fix in the private API helper/server. If it doesn't match BB, then it may be a caching issue on the client

For me when this issue comes up, it is the latter where the address does not match the coordinates.

Do you know what's more updated tho? Like what's more accurate at the current checking time?

The long address field is accurate but the coordinates do not update

That's the same problem that we're having, my bad I probably could have worded my initial comment better

[User8395]

Can confirm that restarting the server does work. However, we should not have to keep restarting the BlueBubbles server just because we want to see where our friends are.

[Abolfazl]

Can confirm that restarting the server does work. However, we should not have to keep restarting the BlueBubbles server just because we want to see where our friends are.

While restarting server works, this is a little overkill. Whenever I have issue of the coordinates not matching the the address description, I just pick one of the contacts, click contact info, close window, go to same contact, click contact info again and it starts reporting correct coordinates.

[User8395]

Can confirm that restarting the server does work. However, we should not have to keep restarting the BlueBubbles server just because we want to see where our friends are.

While restarting server works, this is a little overkill. Whenever I have issue of the coordinates not matching the the address description, I just pick one of the contacts, click contact info, close window, go to same contact, click contact info again and it starts reporting correct coordinates.

Do you mean clicking the name at the top to open the Android Contacts app twice or going to details twice? Because neither worked for me.

[Abolfazl]

Can confirm that restarting the server does work. However, we should not have to keep restarting the BlueBubbles server just because we want to see where our friends are.

While restarting server works, this is a little overkill. Whenever I have issue of the coordinates not matching the the address description, I just pick one of the contacts, click contact info, close window, go to same contact, click contact info again and it starts reporting correct coordinates.

Do you mean clicking the name at the top to open the Android Contacts app twice or going to details twice? Because neither worked for me.

I go to their contact page from Mac Mini

[User8395]

Can confirm that restarting the server does work. However, we should not have to keep restarting the BlueBubbles server just because we want to see where our friends are.

While restarting server works, this is a little overkill. Whenever I have issue of the coordinates not matching the the address description, I just pick one of the contacts, click contact info, close window, go to same contact, click contact info again and it starts reporting correct coordinates.

Do you mean clicking the name at the top to open the Android Contacts app twice or going to details twice? Because neither worked for me.

I go to their contact page from Mac Mini

I see. That's still not good.

[zlshames]

Instead of restarting your server. Does using the Restart iMessage button do the trick from the Connection & Server page in BlueBubbles?

[User8395]

Instead of restarting your server. Does using the Restart iMessage button do the trick from the Connection & Server page in BlueBubbles?

Idk but the issue just fixed itself. I restarted the server app and the icons are updating properly.

[User8395]

Instead of restarting your server. Does using the Restart iMessage button do the trick from the Connection & Server page in BlueBubbles?

Idk but the issue just fixed itself. I restarted the server app and the icons are updating properly.

Nevermind it's messed up again