Not working on Macos26

[gloaysa]

Hi, I did a fresh install of am in MacOs 26 using cargo install am.

I believe AM API has changed, and running am now while music is playing prints nothing to the console.

Commands like am next work, but they also throw an error: 0: 56:60: execution error: Music got an error: Can’t get name of current track. (-1728)

I'm using boringNotch and it seems to have the same issue.

[ryanccn]

It works fine for me on macOS 26; what are you playing (e.g. playlist, album, library)?

[gloaysa]

Thank you for the quick reply. I've tried playing a Radio Station, playlist, single song (not from my library) and album.
I've been trying to debug this on my own. I found this on Apple Forum (the link to the bug they've opened doesn't seem to work).
I've verified my terminal have access to Media & Apple Music too.

[ryanccn]

Unfortunately there's really not much I can do since I can't reproduce this issue at all; if you have more concrete information on how I can fix this for you, please let me know! Keeping this issue open for now.

[gloaysa]

TLDR: It only works for music in your library. If your locale uses comma as decimal separator, it won't work without tweaks.

I kept debugging this. I'll be adding my findings for reference in case someone else have the same issue
.
So far, I've discovered an old bug that affected Big Sur and looks like is back. If the song is not in your library, can't be displayed.

Playing songs from my library resulted on boringNotch (that I keep as control, since the issue is also there) displaying the currently playing song again. am is still not displaying the song info, and keeps throwing the error on next/previous saying it couldn't find the song, even tho it goes to next/prev track.

Downloading the song doesn't have any effect.

How does am behaves when playing music in the library?
Well, now the error is different when toggling, pause, next, previous, song-link. Instead of Can't get name of current track I got invalid float literal. I traced this and will create a PR that I don't know if you'll accept. The core of the issue: in my locale, we separate the decimal part of a Float with a comma , instead of a period .. Of course, .parse::<f...> expects a period as the separator.
The fix is to do a replace every time we try to convert from the raw string. It's more or less safe, since I checked and it doesn't return the separator for the thousands (in my locale, a period), but is verbose.