Open Radar

 
Summary: 

When handling iCloud items, an application is not allowed to load items through use of +applicationMusicPlayer and has to use +iPodMusicPlayer. However, when this happens, the iPodMusicPlayer eats all the remote events and applications have to do dirty things to figure out what the iPodMusicPlayer is doing :( 

MPMusicPlayerControllerNowPlayingItemDidReachEnd isn't reliable enough, as it doesn't specify how it was changed (whether the player was stopped, or skipped forward or backwards). Also, the iPodMusicPlayer doesn't have a currentCollection that I can reference from, only a nowPlayingItem.

Currently, my flagship application Reprise (http://www.appstore.com/reprise/ is incapable of handling iCloud items, which made a lot of users sad. Until I figure out how to get around this, I won't be able to ship a proper iCloud update.

If these events could be forwarded, added to MPMusicPlayerControllerPlaybackStateDidChangeNotification notifications, or even have some sort of MPMusicPlayerControllerNowPlayingItemDidReachEnd event, it would make several people's lives much easier!

Steps to Reproduce:

Call -beginReceivingRemoteControlEvents.

Expected Results:

Some sort of event passed to the iPodMusicPlayer object.

Actual Results:

Watch as iPodMusicPlayer eats the event :(

Regression:

Notes:

I've currently got a tracklist setup, monitor MPMusicPlayerControllerNowPlayingItemDidChangeNotification, and then check the list to try and guess how it changed, however there's far too many variables for this to remain reliable (as a user could manually pick a song in the player, which could also be coming up in the queue, or something).