MacOS > Apple Music > Mini Player > Full Screen Mode kills AirPlay streaming

I am the original poster on this thread, and just wanted to confirm that as of version 13.5.1, Apple has resolved the issue. On my MacBook Air, I can now seamlessly switch to the Mini Player while using AirPlay streaming.

I want to give a shout out to Dominic, the Apple Support representative who I spoke with about the bug. He listened, understood, tested, followed up with the Apple developers responsible for the feature, confirmed when they had fixed it, and emailed me directly to let me know it had been resolved. Thanks!

Thanks for the response Jeff_W. Like you, I also don't know what the cause is -- the most helpful suggestion you made can be found at the end of your post - I will just contact Apple Support.

Regarding:

Since you're using the MiniPlayer in another fashion (in full screen mode), that suits your needs, it may not be the way Apple intended it to be used.

I can see how it might feel helpful to point this out, but it really comes across as a conjectural distraction to the helpful part of your response (i.e.: contact support). More over, it is a convenient oversimplification: Apple designed and developed the app, explicitly including the capability to view the mini player in full screen mode. By definition, this makes them responsible for delivering that functionality. The assertion that it's unclear that Apple intended it to be used this way is right in front of you - the app has the feature! Anyone can click on the full screen window control in the mini player, and the full screen view it provides is obviously intentionally designed and made available by Apple. Apple's own human interface guidelines allow for developers to disallow full screen mode if they want to -- why wouldn't Apple themselves have simply omitted the control for full screen mode, if it were true that they didn't "intend it to be used" that way?

My software is updated routinely. In fact I just updated to 13.2 yesterday, and after restarting, the problem continues to persist.

I will contact support, thanks for the suggestion.

I contacted Apple Support by phone, indicating that I needed help with Apple Music on my MacBook Air, and explained the problem in detail. After listening and confirming that they understood the issue by reading it back to me, they told me they would put me on hold while they check with a specialist. Moments later, I heard a brief ringtone, and a recorded voice told me to hold for the next available support person - as if I had been placed back the original support queue. Five minutes later, a recorded voice told me that all Apple advisors are still busy, but to keep on holding. Eventually a support advisor answered, and confirmed that I was basically starting over. Fine. After re-explaining the issue, they confirmed that the previous support person had mistakenly sent me to the wrong place, and that they would not be able to help me after all. After placing me on hold, they came back and asked me for the software version of my iPhone. I reminded them that the problem is with Apple Music on my MacBook Air. They told me that the support notes for my call indicated it was for an iPhone, and that desktop Apple Music support was a completely different department, and that they would need to transfer me. Back on hold. A few minutes later, Pablo greeted me and asked me for my first and last name. After responding with my first and last name, the line went dead… Wow. I waited; I communicated my call back number, in case they could still hear me, even though I couldn't hear them). Nothing. All told, 30 minute call. This is some dystopian, unprecedentedly horrible customer experience. I just decided I don't care enough about this bug to put any more energy into it, which, let's face it, is exactly why bugs like this never get fixed.

I finally got a support representative on the phone that was technical. After about an hour of testing and reviewing the problem, he agreed that it was a real bug, and offered to confirm with the development team. A few days later. he got back to me and let me know that they agreed it was a bug, and that he had filed the bug. No commitment to prioritize fixing it, but at least it got filed...