Yes this sounds exactly the same. I didn't mention it in my original post but we also have 2 iOS targets as part of the project and those always install fine. This is 100% a macOS issue.

I'm having this issue too. Did you find a solution?

Hi. Is there any update on this? It seemed to be fixed for a few weeks (or at least we didn’t get any problem reports) but over the last few days we’ve had lots of users reporting the issue again.

It's already there in my original post: FB11733455

Hi @JoeKun. I’ve just opened FB10030197 for this. It contains a detailed write up, including log files, which demonstrates the issue. It’s a very real problem: you add tracks to a playlist, get a 204 back (success), then query the playlist and the tracks are not there. I actually opened a TSI for this 2 days ago as it’s critical to my business. So far I’ve heard nothing back.

I discovered this purely by chance (and I shudder to think about what is going under the covers) but I found that if the following line of code gets run before the call to ApplicationMusicPlayer then it all seems to work: let _ = MPMediaQuery.playlists() Clearly this ought not to have any effect at all, but it works for me so I'm sharing it in case it works for others.

Thank you. I wasted an entire day trying to find a non-existent bug in my code before finding this comment. Adding this one modifier to the Navigation view's parent fixed everything.

I saw that post but I'm not sure it's the same thing. My build numbers on both the iOS & macOS versions are (correctly) the same and are exactly what I set them to / what they ought to be. The error message I'm getting back from App Store Connect references the same build number. There's no auto-incrementing going on, basically, as far as I can see. It's more as though there's something now stopping the same build being uploaded to both the macOS & iOS app stores.

Between 4pm & 5pm yesterday (18 June)