Apple Script for Music app no longer supports current track event

Question

Created 1w

Replies 4

Boosts 0

Participants 4

AppleScript for the Music app no longer supports the current track event. Before macOS Tahoe, running the following script in Script Editor would return the current track information:

tell application "Music"
	return name of current track
end tell

However, when I run this script on a device with macOS 26 Tahoe, I receive this error:

"Result: error "Music got an error: Can’t get name of current track." number -1728 from name of current track”

I've tested this extensively, and here are my findings:

Going to the “songs” tab and playing something from there makes everything work.
Playing any song directly will make it work with current track UNLESS this song is NOT in your Music library (either added through Apple Music or uploaded).
If you play a song not in your library, current track is not updated even if you clicked on it specifically.
Playing an album (in your library obviously) makes all the tracks within it appear in current track until autoplay takes over.
Any autoplayed track won’t appear in current track even if in your library (unless: see the last bulletpoint)
Music played through the “songs” tab all appear in current track even if autoplay kicks in. I assume this is because this tab is an iTunes legacy (visually and under the hood) and doesn’t use the modern autoplay. This tab also won’t play non-library songs unlike the “albums” tab which seems to use the correct autoplay and suffers the same symptoms as the “recently added”, “home”, “radio”, etc… tabs.

Is this a bug, or has Apple simply deprecated this functionality?

Answered by DTS Engineer in 855667022

Is this a bug, or has Apple simply deprecated this functionality?

This is one of those “Does it really matter?” moments. If you were previously relying on this feature, does it really matter whether it’s a bug or a deliberate change? The correct path forward is the same in each case: File a bug about the problem.

Please post your bug number, just for the record.

But, yeah, if I had to guess I’d say this is just a bug.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

1w

Recommended

Is this a bug, or has Apple simply deprecated this functionality?

This is one of those “Does it really matter?” moments. If you were previously relying on this feature, does it really matter whether it’s a bug or a deliberate change? The correct path forward is the same in each case: File a bug about the problem.

Please post your bug number, just for the record.

But, yeah, if I had to guess I’d say this is just a bug.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1

Answer 2

DTS Engineer OP

Apple

1w

Based on the explanation you have provided it sounds like the current track is still working as it has in the past with tracks in the user's library but it has not been updated to work with tracks from other sources. Because of that, this could be interpreted as either a bug or an enhancement request.

To work around this change, I suggest enclosing any usage of the current track property inside of a try block so that in cases where using this property fails you can provide appropriate alternative functionality.

Whether or not this is a bug or an enhancement request, I recommend filing a feedback report (ad Quinn has suggested above) and testing your software in system software updates (including beta updates) whenever a new one is made available. And, whenever you test in a new update, please update your feedback report.

0

Answer 3

SrknAdgzl OP

1w

Thank you both for the feedback. I filed a bug report as suggested and the number is here "FB19908171".

To clarify my motivation for asking whether this is intentional or a bug: I'm maintaining AppleScript-based tools that have relied on current track for years, and this change significantly impacts their functionality. Understanding Apple's intent helps me decide whether to:

Implement workarounds and keep investing in this approach (if it's a bug likely to be fixed)
Pivot to alternative solutions if it's a deliberate deprecation

The try block workaround is helpful for graceful degradation, but it doesn't solve the core issue - there's currently no reliable way to get information about non-library tracks that are actively playing through AppleScript.

The inconsistent behavior (works in "Songs" tab but not others, works for library tracks but not Apple Music streams) really does suggest this is unintentional rather than a deliberate API change. If Apple intended to restrict current track to library-only content, I'd expect consistent behavior across all playback contexts.

I'll test this in upcoming betas and keep the feedback updated.

0

Answer 4

peterharte OP

1d

tell application "Music" return name of current track end tell

Works in DB9

0