Rustpush

[devnoname120]

It looks like Rustpush supports Find My! This would make it more robust and improve support (iCloud’s web interface private APIs miss a lot of information such as location reports by other users).

https://github.com/OpenBubbles/rustpush/blob/8eff6251b5bc62dbb179e1f320bfb97fab502b1d/src/test.rs#L658-L664

Here is specifically the structure that contains the location information: https://github.com/OpenBubbles/rustpush/blob/8eff6251b5bc62dbb179e1f320bfb97fab502b1d/src/findmy.rs#L781

The list of locations is obtained by sync_item_positions():
https://github.com/OpenBubbles/rustpush/blob/8eff6251b5bc62dbb179e1f320bfb97fab502b1d/src/findmy.rs#L1137

[kennym]

Thanks for mentioning this! Do you think you could propose a PR? If not, I'll try to investigate this further this weekend

[kennym]

Thanks for the suggestion! I've done a deep feasibility analysis on integrating Rustpush, and unfortunately it's not a great fit for this project. Here's why:

Protocol Mismatch

The core issue is that Rustpush's Find My support and what this project does target different Apple subsystems:

• This project tracks iCloud device locations (iPhones, Macs, iPads) via the iCloud web API — plain lat/lon JSON responses
• Rustpush's Find My accesses the Find My network protocol — encrypted BLE beacon reports (designed for AirTags/accessories and crowd-sourced offline finding), which use P-224 elliptic curve crypto and key ratcheting

Your own iPhones/Macs publish their location through iCloud web services, not through the Find My beacon protocol. So Rustpush can't replace pyicloud for this use case.

Additional Blockers

• No Python bindings — Rustpush is pure Rust with no PyO3/FFI/Python wrapper. Building one would be 6-12 weeks of work due to async Rust (tokio) complexity.
• macOS requirement — Rustpush's default feature requires macos-validation-data via open-absinthe (macOS system frameworks), but our Docker setup runs Linux.
• Immature Find My support — Find My tests are commented out in Rustpush; it's a secondary feature of an iMessage library.
• Auth complexity — Rustpush uses APNs-level auth (push certs, identity keys, anisette) vs pyicloud's simpler web session + 2FA.

Better Alternative

If we want AirTag/accessory tracking (which is what the Find My network protocol provides), FindMy.py is a much better fit — it's a pure-Python implementation of Apple's Find My protocol that would integrate directly without any Rust/FFI complexity.

I'm open to adding FindMy.py as a supplementary data source alongside pyicloud if there's interest in tracking AirTags and accessories. That would be a much more practical path forward.

[kennym]

This (https://github.com/malmeloo/FindMy.py) is actually amazing - I think I can get AirTag support integrated with it. I'll spin up a PR

[devnoname120]

@kennym Here is what Codex came up with after several planning/feedback rounds. Once I was satisfied with the plan it worked for 38m 22s!

#6

I will test soon and see how well it performs :)

[devnoname120]

@kennym Which tool did you use to compute that plan? It looks completely wrong and with a lot of inaccuracies