FindMy icon indicating copy to clipboard operation
FindMy copied to clipboard

Apple's fetch api seems faster than before, but returns less location reports

Open lovelyelfpop opened this issue 3 months ago • 10 comments

This api(https://gateway.icloud.com/acsnservice/fetch) responses 60% faster than before, but the number of returned location reports has decreased significantly.

Half my tags' locations not get updated since one or two days ago.

And the new api(https://gateway.icloud.com/findmyservice/v2/fetch) returns empty response for half of my requests, even http status code is 200.

Did Apple change something again?

lovelyelfpop avatar Sep 28 '25 02:09 lovelyelfpop

In the past, if a key was always with a certain Apple device, this Apple device would only report its location a few times in the beginning, and then almost never report it's location later.

Now it seems that if a key has been used(has reported by any Apple device), it will not be reported by all Apple devices.

lovelyelfpop avatar Sep 28 '25 07:09 lovelyelfpop

Interesting find! I have yet to start experimenting with the new endpoint so I can't say anything sensible about it at the moment, but it definitely looks like apple is trying to restrict the way we use it 😒

biemster avatar Sep 28 '25 11:09 biemster

In the past, if a key was always with a certain Apple device, this Apple device would only report its location a few times in the beginning, and then almost never report it's location later.

I don't think is accurate? I have a friend with an iPhone who carries one of mine, his iPhone definitely seems to report the tag repeatedly. I've also got one in my back garden that would only be in range of a couple of neighbours, whose phones reliably report it in

fz6 avatar Sep 28 '25 12:09 fz6

It's very likely that a software update for iOS is responsible for this, so it might be that the phones of your friend and neighbors did not update yet? I'm just speculating here, we'll have to see if we get more reports like this.

biemster avatar Sep 28 '25 12:09 biemster

I gave some tags to some of my friends, and they all said that since September 27th, the locations of these tags have rarely updated.

I debugged the number of reports returned by Apple api, and it was less than half of what it was before.

After some test, I found my iphone 8 (ios 16.7.11) no longer reports my tags' locations, even new tags with new keys. When I went to the office, my tags works again, there are a lot of iPhones in my office and maybe part of them can report tags' locations.

Maybe Apple is planning to retire old iPhones.

But some of my friends use iPhone 14 or iPhone with iOS 26, and the tags around them cannot update locations either. It's really weried.

lovelyelfpop avatar Sep 29 '25 00:09 lovelyelfpop

@lovelyelfpop What f'ed me over was a new format of the encrypted location reports. The data grew from 88 bytes to 89 bytes over time.

Maybe that has something to do with new iOS versions, and your problem...

dakhnod avatar Sep 29 '25 10:09 dakhnod

I personally haven't experienced issues with a reduced number of location reports, but the empty response thing appears to be an issue on Apple's side. The FindMy app on macos is also running into it. The 'fix' is to just retry the request in a few seconds or so.

malmeloo avatar Sep 30 '25 11:09 malmeloo

I'm also experiencing this error in my application. The workaround suggested by malmeloo works, but very few reports are coming back. But if the FindMy app on macOS is also experiencing this problem, then it does indeed seem to be an Apple issue. I'm surprised that the problem has persisted for so long... isn't Apple usually quicker to fix these kinds of things?

merasil avatar Sep 30 '25 12:09 merasil

Apple is not quick on these things at all. When iOS 17 broke FindMy reporting completely (#40) , it took them to 17.4.1 to get it fixed. 😒

biemster avatar Sep 30 '25 12:09 biemster

Yeah, I wouldn't bet on Apple to fix this quickly. Apple devices are continuously querying device locations while the FindMy app is open (and possibly also when it isn't?), so this issue is unlikely to have a real impact on their own devices.

malmeloo avatar Sep 30 '25 12:09 malmeloo