View Issue Details

IDProjectCategoryView StatusLast Update
0020371MMAGeneralpublic2023-11-22 13:06
Reporterrusty Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version2.0.0 
Target Version2.0.0Fixed in Version2.0.0 
Summary0020371: 'Dirty' install of MMA results in skipped or failed permissions / crash on startup
DescriptionIf the user uninstalls MMA and retains the DB, then upon installing and running build 1154, MMA always crashes and then shows the Welcome to MediaMonkey / Folder Permission granting screen (i.e. it seems to skip the initial screen prompting for access to Music/Audio).

Tested multiple times with S10/Android 12.
Steps To Reproduce1 Install MMA and sync some tracks
2 Install MMA Pro (probably not relevant)
3 Uninstall MMA but retain data
4 Re-install MMA
--> Crash screen briefly appears
--> Welcome to MM / Folder grant screen appears ! (having skipped prompting for other permissions)
TagsNo tags attached.
Fixed in build1157

Relationships

related to 0020330 resolvedrusty Photos and video access permissions are requested 

Activities

rusty

2023-11-15 02:17

administrator   ~0073495

Last edited: 2023-11-15 02:19

On further testing, it seems that MMA briefly crashes every time it starts (I'm guessing that the required permissions are missing but MMA crashes before it's able to request them??) and then continues running.

Debug log: SX611S9YBQ (manually generated subsequent to the crash).

rusty

2023-11-15 17:39

administrator   ~0073499

Last edited: 2023-11-15 17:48

On a clean install, it presents the license and then prompts 'Allow MediaMonkey to access photos and media on your device?". And it never crashes subsequently.

Note that both clean and dirty installs prompt for folder permissions.

So the bug is likely related to the fact that for some reason, on a 'dirty install' MM doesn't show this prompt.

rusty

2023-11-15 19:36

administrator   ~0073500

Last edited: 2023-11-15 21:08

I've subsequently done a clean installation, and then tried to replicate the crash, but am unable to. So it's unclear what was triggering the crash.

The only anomaly that I do consistently observe now with every 'dirty install' on the S10, is that:
- 'dirty installs' (i.e. uninstalling MMA but retaining data, and then installing MMA from the play store) consistently fail to prompt the user to grant access to Music and Media.
- when I attempt to grant access to the internal /Music folder, the following message always results "Path 'Internal storage/Music was not requested. Please choose fro..." (the toast in truncated).

martin

2023-11-15 21:09

developer   ~0073506

1)Runtime permissions are kept: So access to Music and Media is not asked again. (SX611S9YBQ and my testing confirm that permission is granted)
2)TreeUri permissions are not persisted (access to folders)

Re: "Path ... was not requested" please send log after that

rusty

2023-11-15 21:10

administrator   ~0073507

Interestingly, when I test an Android tablet running Android 13, and a Pixel 2XL running Android 11, the issue doesn't occur.
Maybe priority should be reduced.

martin

2023-11-15 21:13

developer   ~0073508

Btw on the first video, there is a crash dialog which is covered by the home screen activity. If go from the home screen by back action then the dialog should be still visible and you should be able to send crashlogs.
Or you can enable "Send crash logs automatically" in Options/General for next time.
I cannot replicate it either. So I agree that we can reduce priority.

rusty

2023-11-16 15:32

administrator   ~0073529

I can no longer replicate the crash :-(

But here's a debug log for the 'path not requested' issue from 0020371:0073500
AVTJRSM9HC

Reducing priority.

martin

2023-11-22 12:55

developer   ~0073606

Last edited: 2023-11-22 13:06

The 'path not requested' issue fixed in build 2.0.0.1157