BluOS app error message

Just got this reply from Bluesound:

Brian,
 
Thank you for contacting The Bluesound Support Crew.
 
Following discussions with our Engineering team regarding your specific issue, they have replicated the issue in our labs. Our Engineering team will conduct further investigation and provide a fix for this issue in an upcoming firmware update.
 
Unfortunately, we in technical support do not receive timelines for future development and releases, so I cannot provide a definite date for when this update will be available. Nevertheless, please be assured that our Engineering team is diligently working to resolve this issue as promptly as possible.
 
Our team may contact you directly if they require further details regarding the issue you're experiencing.
 
I apologize for not having an immediate solution for you.
 
Thanks for #LivingHiFi.
 
Regards,
Charmain K.
The Bluesound Support Crew

Interesting bug. I have had it happen, but only with Qobuz. Not happening with Amazon Unlimited Music. But since Bluesound has addressed and confirmed it, it appears to be on their end. I hope the fix is soon so I can use Qobuz again. 

I have a similar issue with BlueOS streaming Amazon Unlimited into a NAD 3050LE. My NAD will be streaming from A-U and then suddenly power down. I have triangulated the potential culprit to the Apple TV that is also hooked to the NAD via e-ARC. I believe that the Apple TV is occasionally communicating with the NAD. The issue is almost guaranteed to occur about 15 minutes after turning off Apple TV and switching to music. 

@gingerman  Thanks, that’s good info. I have Amazon Prime but never used their streaming even though it’s free. Think I’ll switch to that for now until this bug is resolved. And yes it does appear to be on Bluesound’s end. I also am awaiting a response from Qobuz. Curious to see their reply on this…

@kingbr I know a lot of folks, myself included, are having drop out issues with Qobuz played through Roon over the past 2-3 weeks that seem to be getting worse. I read on Roon forums where this is related to Qobuz’s migration of files to new servers. It seems random but is very annoying. I suspect you are seeing a similar manifestation of this migration as alluded to by you above. Hopefully it‘s soon a self resolving issue.