Page 2 of 2

Re: Casting: MMA does not trigger device discovery [#20861 #21602]

Posted: Fri Nov 07, 2025 5:30 pm
by drunknmonkey
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 :oops: , 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

Re: Casting: MMA does not trigger device discovery [#20861 #21602]

Posted: Mon Nov 10, 2025 7:37 am
by martin.bohac
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.

Re: Casting: MMA does not trigger device discovery [#20861 #21602]

Posted: Fri Nov 28, 2025 10:21 pm
by drunknmonkey
I did not see this bug appear again since updating to build 1.2.1.1288.