This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update dependency pyright to v1.1.360
• fix(deps): update dependency aiohttp to v3.9.5
• chore(deps): update dependency sphinx to v7.3.7

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Is OfflineFindingScanner meant to work on windows?
If so, it doesn't and also it doesn't give a graceful error message

Hi,
How technically feasible is it to use this project to work with official AirTags or other Find My devices? Already working AirTag clones are being sold for $2-4 a piece on Aliexpress, so I don't see a point in spending a lot of time messing with flashing, firmwares and all of that OpenHaystack stuff, when I can just buy a working "AirTag" for so cheap.

Support trusted device 2FA. Need someone with an Apple device to test this for me, so please let me know if you're willing to help!

Apple appears to have locked down the https://gsa.apple.com/auth endpoint, as it now returns a generic 403 error every time across multiple accounts, IPs and anisette generators. This isn't a huge deal, but it was used to resolve the available phone numbers for 2FA and their corresponding IDs, which are necessary for submission.

I have just tried an (unreleased) fix which simply takes the phone numbers from the SPD data in the initial auth response. This works but there are no IDs in that data, so it's currently just incrementing starting from 1. That should work for most accounts with only a single phone number.

Maybe it's worth looking into an alternative source of this data altogether; calling that endpoint had the annoying side effect of implicitly requesting a 2FA code every time you called it, which is not really compatible with the library's API design.

Context: #4 (comment)

There has been at least one case where a location report from a real AirTag was not decodable. Maybe this an issue on Apple's side?

In any case, this edge case should be handled better than straight up crashing.

Example:

2bd8e645000504dee6a88ab4580e4c90dcacc62e0efae57a003a1bac1212ba670398be61cb648e08417cf3714ee0429f961793aa645600a7f69807e215292da3a6bda511953cb15b4840de16e26c17651eef760e77fa4b2ca5

In case anyone is interested, I've started a Swift port of this library
Still a lot to do since only the KeyPair and Accessory classes are ported but that's enough to generate to the primary and secondary keys for any date from the original private key and shared secret

SwiftFindMy

I'm trying to get data only for one day by setting startdate and enddate for the search.
This was the query. You see it's 24 hours.
{'search': [{'startDate': 1712449083967, 'endDate': 1712535483967, 'ids':...
But the Apple server always returns a week of data.
Is the format wrong?
Your code in accounts.py changed:

def fetch_last_reports(
        self,
        keys: Sequence[KeyPair],
        hours: int = 1 * 24,
    ) -> MaybeCoro[dict[KeyPair, list[LocationReport]]]:

Support local anisette header generation using pyprovision.

Currently, reports.py:fetch_reports() creates a new HTTPSession for every lookup, because it doesn't know when to close it. This function should probably be converted into a class to make it stateful and add a close() method to it, just like BaseAnisetteProvider and the gang.