View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020861 | MMA | UPnP / Casting | public | 2024-04-18 15:00 | 2024-04-18 15:25 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| Product Version | 2.0.0 | ||||
| Target Version | 2.0.0 | ||||
| Summary | 0020861: Casting may fail to discover available casting destinations | ||||
| Description | If 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 Reproduce | Reported at: https://www.mediamonkey.com/forum/viewtopic.php?t=106051 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
