Skip to content

OpenTagViewer AirTag Exporter 1.5.1

Choose a tag to compare

View all tags
@parawanderer parawanderer released this 16 Sep 16:09
· 53 commits to main since this release
exporter-v1.5.1
bf9cf9b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Simple cross-OS GUI Application for exporting FindMy devices to a .zip file that can be imported into the OpenTagViewer app.

Summary

Changes

[!IMPORTANT]
If signing in has been failing with 429 Too Many Requests, this release fixes it. Update and try again. Nothing was wrong with your Apple ID or your password, and you were not locked out.

Changed:

  • Exports are now protected with a passcode by default. The wizard shows you a code when it writes the zip, and whoever opens it needs that code. Send it separately from the file — a bundle holds the keys to your tags, and anyone who has both has them too.

    A locked export needs OpenTagViewer 1.1.0 or newer to open.

Fixed:

  • Signing in could fail with 429 Too Many Requests. Apple began refusing the second of the two requests a sign-in makes whenever both were sent over the same connection, which is what this program was doing. It now uses a fresh connection for each one. (#206)

    Found and diagnosed by @LiamJ74.

  • Signing in could time out five seconds after the verification code. The step that unlocks your keychain was only ever given five seconds to answer, however long the rest of the program was allowed to wait — not enough on mobile data or a slow link, and it arrived as a bare TimeoutError naming a setting you had no way to change. It now waits as long as everything else does.

  • On Linux, signing in failed with a certificate error right after the verification code was entered. The downloaded program had no list of certificate authorities to check Apple's servers against, so the step after the code could not connect. It now carries its own. Setting SSL_CERT_FILE by hand is no longer needed. (#206)

  • Reading your tags from iCloud could stop with "CloudKit did not return a user id". One of the two tokens that request needs was not being sent, and Apple answered with an empty reply rather than an error.

    Found by @LiamJ74.

  • Being offered terms of service that do not exist. If Apple accepted your password and code and then refused to open iCloud for the account, the exporter treated it as pending terms — so it went looking for documents, found none, and left you no further forward. It now says what actually happened, quotes what Apple said, and points at the one remedy other projects have found for it: signing in at appleid.apple.com and filling the account out, which is usually what accounts that have never been used with an Apple device are missing. (#221)

    The remedy is Macless Haystack's finding, not ours.

Assets 7
Loading