I did not see this bug appear again since updating to build 1.2.1.1288.

Hi,
Unfortunately, our crash report server was down over the weekend, and your logs are lost.
I am unable to replicate your issue on my devices, but I have updated the Cast library to the latest version in build 1.2.1.1288.
If the issue persists in this build, please send your logs again.
Thanks.

Could please someone look into this?
I just switched to my new smartphone Samsung S25+ and this problem shows up even more often.

I just wanted to cast a song to my speaker "Teufel Bad". I opened MMA and started local playback, opened the cast dialog which only showed 2 of my 5 casting devices. I waited a few seconds to let search finnish - nothing happened. As luckily "Teufel Bad" was one of the 2 "present" devices, I tapped on it but MMA could not connect. I repeated this procedure multiple times. Sometimes MMA even shortly showed more devices but then switched back to only the 2 devices. I gave up frustrated , opend VLC app, opened it's cast dialog and after a few seconds it showed 4 of the 5 casting devices and connection to "Teufel Bad" worked smoothly. (not sure why 1 of the devices is not available in this app). Going back to MMA casting still does not work.

My feeling is, that MMA maybe triggers the device discovery but does not use the found devices in it's list. Maybe it shows some outdated cast device search results?

Log-ID: 1AMUBIUWK8
Log-ID: E6FJTI8XW4

Hi!
I am now seeing another form of this bug.
My understanding of the cast button is:
If I press the cast button it shall show the available cast devices and trigger device search in background.

Two days ago I ralozed that each time I press the cast button it shows an empty list and triggers device discovery which refreshes the list after a few seconds with the found devices. If I now go back and press the cast button again all that starts over again... The list is empty and device discovery starts.
MMA should remember the list of devices it found before.

I sent multiple logs today, this was the last: V1JKJA3RHV

While writing this report MMA remembers the list of found devices again. So unfortunatelly it is not 100% reproducible.

Hi, thanks for your logs.
The issue is tracked as https://www.ventismedia.com/mantis/view.php?id=21602
The fix should be included in the next BETA.

Log ID: TZSIU8VRCL
Description: MMA does not find casting speakers. Other apps do

Log ID: XUYISPQ4MX
Description: casting device list got cleared after it already showed devices 5 minutes before.

The problem is showing up again.

Log ID: WBSS5APF59
Description: Cast device list gets filled only after several tries. Another app already shows all casting devices.

Thanks for your sign of life (and of course the fix)!

This should be fixed in the new 1202 beta. Thanks!

-Rusty

It feels like device discovery is triggered in the background but a refresh of the view is missing.
If I stay in the empty casting devices view it will never refresh with the found devices. I tested and waited 2 minutes. But if I switch to another view like Playlists view and go back to the casting devices view the found devices are instantly shown.

So I have got a workaround, but it would really be nice to see this issue fixed. I am facing this issue at least once a day every morning. Sometimes a second time in the afternoon.

Log ID: 7QZH3434AC
Description: no casting devices in list after 2 minutes

Interestingly the casting device list is always filled when returning from the "send debug logs" view.

The hasn't been an Android update in a while.
This bug is really annoying.

Is this still beeing worked on?

After sending the logs of my last post MMA suddenly found the chromecast speakers.

I subsequently sent a log: YJQSRUN9WI