View Issue Details

IDProjectCategoryView StatusLast Update
0020861MMAUPnP / Castingpublic2024-07-27 10:59
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Product Version2.0.0 
Target Version2.0.1Fixed in Version2.0.1 
Summary0020861: Casting may fail to discover available casting destinations
DescriptionIf one runs MM immediately after waking the device and then taps the cast button, it sometimes fails to discover any available casting destination devices.

1 Run MM
2 Tap the Player
3 Tap 'Cast' button
--> 'Cast to' dialog appears with 'Loading...' indicator
--> No device discovered
Debug log from S24: W1RAILMYCQ (after waiting a few seconds and trying again on the S24, discovery succeeded)
4 Tap 'Cast' button again
--> 'Cast to' dialog appears and immediately shows 'no device' discovered
5 Repeat step 4 two more times
--> Fails in the same manner
Debug log: 7LDKEPLN3S
6 After submitting the debug log, tap the 'Cast' button again
--> Success

I've tested this issue on 5 devices and the bug occurred twice. My suspicion is that there's a bug in the 'Cast to' dialog in that it sometimes fails initial discovery and that once it fails, subsequent attempts always fail until some other activity occurs (i.e. it might be that opening the Debug log dialog was sufficient, OR it might be that the network activity associated with submitting the debug log was sufficient).
Steps To ReproduceReported at: https://www.mediamonkey.com/forum/viewtopic.php?t=106051
TagsNo tags attached.
Fixed in build1200

Activities

martin

2024-06-27 15:19

developer   ~0076188

Fixed in build 2.0.1.1200

peke

2024-07-27 10:59

developer   ~0076450

Verified 1201

I have not seen discovery timeouts on MMA in 1201 and it could happen on earlier builds when trying to cast to Nexus PLayer and Xiomi BOX S