App: No last location known

[walker333]

App version

1.0.5

Phone and Android version

xiaomi redmi note 13 pro 5g android 16

Where does it go wrong?

The map — no locations, or wrong ones

What happened

I made all the mentioned steps and finally imported the data for 2 macs, 1 ipad and 1 airtag. However it does not show anything on the map and
if I select My Devices, it shows "no last location known" for each one of them.

Below is the log file
OpenTagViewer-1787668684111.log.txt

Which exporter made the zip?

OpenTagViewer-Exporter-1.3.0-macos-arm64 keys:from my apple account

The log

Before you post

• If I attached a log, I have had a look at it and taken out anything personal the app missed.

[parawanderer]

Hi, this is most likely part of a set of issues that should be migrated with the pending 1.1.0 release of the app.

That release will fix a few mechanisms that cause this sort of problem:

• external anisette server related issues (due to replacing the external anisette server with a local anisette process)
• expired auth related issues
• the tags only broadcast to the FindMy network when they are decoupled from their "owner" device. When they're next to their owner device they don't broadcast to the FindMy network and only locally over BLE. App version 1.0.5 didn't support local bluetooth scanning for the tags yet, but the work that's being done by @ubrt in Find, ring and watch an accessory over direct BLE #139 will likely give you a higher location data level parity to the frequency of updates of iOS devices' native FindMy app

So once app release 1.1.0 is out I recommend you update to that and check if that fixes your problem.

What you can do for now is change the Anisette server to a different one or a personal one

[parawanderer]

Right so I just went through the log, and it actually rules out most of what I guessed above, so correcting the initial assumption here (or rather specifying):

It looks like in this case your sign-in is fine. The log says Login State: LoginState.LOGGED_IN and contains no authentication error at all. So changing the anisette server in your case is unlikely to change anything.

Otherwise, there are three separate things are going on:

1. Your AirTag had a location report older than 24h (which 1.0.5 does not render)

Got 8 raw reports for 78EF4437-…
  -> 0 reports after filtering to last 24h

Apple returned eight positions for it. 1.0.5 only asks for the last 24 hours on a tag it has never fetched before, so all eight were discarded and the map drew nothing. This is already fixed for 1.1.0: a tag with no history gets seven days, which is everything Apple keeps.

It's not necessarily very useful to get a report from 4 days ago when your iPad shows that the last report is from "just now", but the app will show whatever it can now.

2. Regarding the two Macs and the iPad

An AirTag is found only by strangers' iPhones passing it and uploading an encrypted report. This is the only Apple API level mechanism AirTags use for sharing their data over the network, and currently this app only reads these reports.

Macs, iPads, iPhones, etc. are a different situation. Those report their location/position to iCloud directly (rather than the FindMy network that AirTags use) and usually report a Wifi based position too. Apple's Find My app reads and shows those. The weird thing is that Macs & co can report to the FindMy network as well under specific circumstances, but mostly don't do that because the fastest way for them to produce location updates is to report to iCloud while directly connected to the internet.

Anyways - this app can't speak to that service yet (#131). A Mac/iPad will only appear on this app at all only when someone happens to walk past it while it's asleep and broadcasting, which is rare and arbitrary, so it looks broken while working exactly as designed.

In 1.1.0 your own Apple devices are hidden by default for that reason, with a setting that explains what turning them on gets you. #131 is the issue to implement proper support, left to whoever is interested in implementing that.

3. In 1.0.5 even a found tag lags the real Find My app anyways

A tag sitting near its owner's Mac or iPad doesn't broadcast to the Find My network at all: it talks to those devices directly over Bluetooth. There is genuinely nothing on Apple's servers to fetch in that case, however far back we look. Apple's own app covers it because your iPhone is in the room.

That's the missing feature, and it's why 1.1.0 isn't out yet — @ubrt is building local Bluetooth scanning in #139, and the release is waiting on it rather than shipping without it.

---

TL;DR (which remains the same as the shorter triage response above in practice): when 1.1.0 is out it should improve your AirTag on all three counts at once. The Macs and iPads are #131 and further off as I myself have no plans to look into that topic right now (but there seems to be community interest in the app, so somebody could likely make it work if they dedicate some time to it).