View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020184 | MMA | UPnP / Casting | public | 2023-08-09 14:58 | 2023-09-14 19:48 |
Reporter | rusty | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | sometimes |
Status | closed | Resolution | fixed | ||
Product Version | 2.0.0 | ||||
Target Version | 2.0.0 | Fixed in Version | 2.0.0 | ||
Summary | 0020184: 'Remote client connected' string appears without running MM | ||||
Description | A user installed MMA and without running it, it indicated "remote client connected". This is problematic because it gives the impression of a security issue since: - It shouldn't happen if the user didn't run MMA - MMA doesn't currently have any functionality that would explain this message It's unclear whether this is a functional bug, a string bug (wrong meaning), or both. | ||||
Tags | No tags attached. | ||||
Fixed in build | 1101 | ||||
|
An external client is browsing MMA content (e.g. AndroidAuto). In this case, MMA PlaybackService is running in the background and must show a notification. Usually, MMA shows PlaybackNotification with current track metadata. In this case, there is no current track(now playing is empty) and it shows a simple notification with the text "Remote client connected". Should I change the text or add some description? |
|
I guess that it would be less surprising if MMA communicated what was being connected so that it doesn't seem like a security issue. e.g. Remote client (Android Auto) connected. Remote client (Bluetooth) connected. |
|
In this way it cannot be distinguished, our service is bound by a system that says only that there is some client that wants to browse our content. There can be multiple clients and they can browse at the same time. This is a very rare notification, so something generic should suffice. For example. Remote client connected. Client like AndroidAuto/Blutooth is browsing MMA content. What do you think? |
|
OK. How about: Player connected Sharing content with Android Auto/Bluetooth device. |
|
Fixed in build 2.0.0.1101 |
|
Verified 1101 For me happens when connecting to head unit, info is clear. |