View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020329 | MMA | General | public | 2023-11-06 16:24 | 2024-11-13 20:20 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 2.0.0 | ||||
| Target Version | 2.0.2 | Fixed in Version | 2.0.2 | ||
| Summary | 0020329: Remove the Permission for access to Contacts | ||||
| Description | Currently, 'Contacts' access is required for assigning a ringtone to a contact. i.e. the user can select a track in MMA and Set as > Assign to Contact. Unfortunately, this requires the 'Contacts' permission which is considered anomalous for Media apps (and results in some users getting the impression that MMA is doing something untrustworthy). Would it be possible / make more sense to instead to allow MMA to be called via Contacts > ContactName > Set Ringtone > Complete action using MediaMonkey, so that MediaMonkey would not require the Contacts permission? Aside: the same issue applies to the 'Camera' permission used for QR Code scanning for Server configuration. But there's probably not a solution to that, short of removing the functionality. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1221 | ||||
|
|
Implemented Part 1) Assigning ringtone from the external app: Contacts > ContactName > Set Ringtone > Complete action using MediaMonkey (build 2.0.2.1220) If everything goes well, The 'Contacts' access permission will be removed in the future version. |
|
|
Each time I try to set a contact ringtone, MMA crashes (4 crashes sent from an S24 Plus (android 14) at around 5:20pm). 1 Open Contacts 2 Select a Name 3 Tap Configure > Contact Ringtone > Complete action using:MediaMonkey (just once) --> MediaMonkey opens 4 Select a track --> No change to the ringtone! 5 In Configure contacts, Tap Contact Ringtone > Complete action using:MediaMonkey (just once) --> MM crashes! EDIT: tested the same on a Pixel 5a (Android 14) with the same results. |
|
|
Fixed in build 2.0.2.1221 |
|
|
Verified 1221. |
