macOS Sonoma 15.4 Developer Beta update non functional with app

[TrueBlueFoxx]

macOS Sonoma 15.4 Developer Beta on MacBook Pro M4 Max does not register Apple Music playing. Tried uninstalling and reinstalling, restarting MacBook and no luck.

[ungive]

Thanks for reporting! Could you share your log file?

It's located here: ~/Library/Application Support/Music Presence/presence.log

Also what do you see in the media control panel? Is there any indication that music is playing? You can see what it looks like on Mac here: https://imgur.com/a/YDQegwW

[TrueBlueFoxx]

I am unable to find the log on my Mac, mainly cause idk where to look but that's the other image you will need.

[TrueBlueFoxx]

Ok so I did find it finally. However Music Presence does not have its own file here. In fact most of my apps don't which amazes me.

[ungive]

You probably opened /Library/Application Support, not ~/Library/Application Support. The latter is in your home folder, e.g. /Users/username/Library/Application Support. The ~ represents your home directory.

[ungive]

Another user reported a similar problem on the Discord server using macOS Sequoia version 15.3.1.

The logs contained nothing useful (no media players detected, no errors, no warnings).

[TrueBlueFoxx]

presence 2025-02-25T16:09:02.681Z INFO Application startup, version 2.2.8
presence 2025-02-25T16:09:02.681Z INFO Using locale en_US.UTF-8 (US) instead of the default en_US
presence 2025-02-25T16:09:02.681Z INFO Loading players from local assets
presence 2025-02-25T16:09:03.215Z INFO Successfully updated media players
presence 2025-02-25T16:09:03.215Z INFO Loading players from local assets
presence 2025-02-25T16:09:04.805Z INFO Discord: Connected

These are the recent logs from it. No detection and I am actively playing music.

[ungive]

Thanks! Try installing Spotify and see if it's not detected too, please.

[ungive]

It looks like they're moving stuff around with the now playing info, which might have broken a few things that might get fixed later (hopefully). Please let me know if this issue persists with further beta release of macOS!

I'll only start looking into this when it continues to happen in a stable (non-beta) macOS update.