Broken in Sonoma 14.4 beta

[airy10]

Files format changed in 14.4 beta and is now encrypted data

{
"encryptedData" => {length = 44230, bytes = 0x22a623ed ef7ccab4 b424d3f3 b868e6e2 ... 3eb17138 2e3b3c94 }
"signature" => {length = 64, bytes = 0x6e3ccac7 4263126f 31b93519 9a3c02a5 ... effee5ec d8986c56 }
}

[Flintr]

Broken in 14.4 release

[MartinPham]

I've just updated and saw the problem, trying to work on the changes.
Thanks for reporting!

[airy10]

You can check
https://gist.github.com/airy10/5205dc851fbd0715fcd7a5cdde25e7c8
https://github.com/airy10/FindMyDevices
which has some decoding code for the new files format

[lennarto]

Is this related to the "FindMySync may need your permessions to access ~/Library/Caches/com.apple.findmy.fmipcore" error coming in 14.4 release?

[bubez81]

yes

[MartinPham]

new build is up! https://github.com/MartinPham/FindMySync/releases/tag/latest

Thanks a lot to @YeapGuy and @airy10 !

[airy10]

This change is needed to run on my machine : (else getting the password fails and my Beacons dir name is different)

airy10@1f7ef12?diff=unified&w=1

[Flintr]

The new build works for me! Thanks

[geoffmyers]

Thank you so much for developing this app.

Unfortunately, the latest development build immediately crashes for me on macOS 14.4 (23E214). Here is the error report:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               FindMySync [8196]
Path:                  /Applications/FindMySync.app/Contents/MacOS/FindMySync
Identifier:            mph.am.FindMySync.FindMySync
Version:               1.0 (1)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2024-03-18 06:31:46.9353 -0700
OS Version:            macOS 14.4 (23E214)
Report Version:        12
Anonymous UUID:        D8EB43C2-5D11-56F1-5026-16B7F39E2D9F

Sleep/Wake UUID:       0DE4E837-34DF-4FF9-8A5A-71AB87F9647F

Time Awake Since Boot: 36000 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process:   exc handler [8196]

...

More details:

• Find My app is already running when launching FindMySync
• FindMySync has Full Disk Access enabled in System Preferences
• Deleting FindMySync preferences file in ~/Library/Preferences does not affect behavior
• macOS is running in a KVM-OpenCore environment

[s0ftice]

upgraded to the latest build on macos 14.4, now I'm getting
Cannot parse beacon record: The file “SharedBeacons” couldn’t be opened because there is no such file.
under Status.

I can't find a file named SharedBeacons anywhere in my ~

FindMySync also keeps asking for Grant permissions repeatedly. "Open" a specific folder does not seem to have any effect, I tried ~/Library/Caches/com.apple.findmy.fmipcore and ~/Library/com.apple.icloud.searchpartyd

everything worked fine pre-14.4.

[MartinPham]

thanks for the report, i will try to check it soon

[MartinPham]

ok I've pushed a new update, please kindly check at https://github.com/MartinPham/FindMySync/releases/tag/latest
with the new build, I've created a new config to add beacon decryption key, which could be retrieve by run

/usr/bin/security find-generic-password -l BeaconStore -g

on Terminal, and take the "gena" value (it should look like 0xABCDE...1234)

By default, it will try to fetch the key from keychain, or from the above command.

[chris24walsh]

This is working for me now, thanks for the updates! However, not sure if it is relevant to this build or not but updates to HA are not working.

[<...device id...>] Data sent: HTTP 401

I get errors like the above for all devices. I've tested the long-lived token I generated for this, it works using curl.

[airy10]

Latest one is working fine here 👍

[geoffmyers]

Latest one is working fine here 👍

Same here! Thanks for your great work! 😄

[chris24walsh]

Seems my issue is unrelated one then, I'll open a new issue for it.

[airy10]

Unfortunately Apple broke it again in macOS 15 beta by making the password only readable by the com.apple.icloud.searchpartyuseragent access group