cleanup macOS Catalina + Big Sur Sandboxing access permission dialog

Bug #1921541 reported by Foss-4
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Committed
Medium
Daniel Schürmann

Bug Description

Current Dialog:

Due to Mac Sandboxing, we need your permission to access this file:

After clicking OK, you will see a file picker. To give Mixxx permission, you must select " to proceed. If you do not want to grant Mixxx acces click Cancel on the file picker. We're sory for this inconvenience.

To abort this action, press Cancel on the file dialog.

No | Yes

Thoughts
- is this about general access to the harddrive and the tracks? If yes, there is no need to reference a specific file, so this should be rephrased.
- if it is indeed about a specific file, that file should be shown
- OK and Cancel are not the options given in this dialog. So either the buttons need to be correctly named or the text needs to be re-written
- don't be sorry for this inconvenience - this is macOS defaults and every app accessing files shows such a dialog. By now users are familiar with this. Why should anybody be sorry for better privacy protection for users?

Tags: macos
Revision history for this message
Foss-4 (foss-4) wrote :
Revision history for this message
Be (be.ing) wrote :

When do you see this specific dialog?

Revision history for this message
Foss-4 (foss-4) wrote :

Saw it on each mac once after installing 2.3 I think. I am not sure what triggers this but would assume this is related to the fact mixxx is now notarized and maybe Apple applies different rights management to notarized software.

It is a bit hard to say as before copying the mixxx database to this specific mac I saw the dialog on, mixxx on that mac was stuck in that dead end dialog where scanning the covers resulted in a crash for both selecting yes or no.

Looking at system preferences > security > privacy > files and folders Mixxx is listed with permission to access both Downloads and Documents folder (the latter where music files are stored on macs). Mixxx is not listed in Full Harddrive Access so I assume those two permissions where the ones Mixxx is asking for with this dialog.

It is also interesting that this seems to be a custom dialog, but I would expect macOS has standard dialogs that should be used for asking for file access permission.

Revision history for this message
Foss-4 (foss-4) wrote :

Actually seeing this dialog on every launch on this 10.15.7 mac. Clicked yes, clicked no, doesn't matter, dialog keeps showing on launch.

tags: added: macos
Revision history for this message
Daniel Schürmann (daschuer) wrote :

Can you file a second bug for the 10.15.7 issue? This is a critical issue, because it makes Mixxx useless on this version of MacOs.

This bug can be closed soon. Just propose an improved text and we will integrate it. Here or as a GiHub pull request. The test is defined here:
https://github.com/mixxxdj/mixxx/blob/c8f148eafcb868e4a88ebfce65c5e9b08724e912/src/util/sandbox.cpp#L110

Revision history for this message
Foss-4 (foss-4) wrote :

There are various problems with this dialog outlined in the initial report and without info about those rephasing is not possible.

Besides those question the suggested file picker does not show for me when clicking "Yes" and even when clicking yes on next relaunch the dialog re-appears. So besides rephrasing, this dialog does not seem to do what it claims to do.

Have no insight, but aren't those macOS permission dialogs default dialogs that are created by xcode? https://developer.apple.com/documentation/security/app_sandbox

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Next report about non-working migration of application data, maybe related:

https://mixxx.discourse.group/t/macbook-pro-runs-very-hot-when-using-mixxx/22382

Let's just drop macOS support if no developer steps in ;) Seriously, these issues cannot be resolved without an Apple device at hand.

Revision history for this message
Foss-4 (foss-4) wrote :

Update on this specific error, which I think should be kept separate from the two recent discourse reports:

* https://mixxx.discourse.group/t/macbook-pro-runs-very-hot-when-using-mixxx/22382/
* https://mixxx.discourse.group/t/trouble-with-mixxx-on-mac-book-pro/22408

My setup: use mixxx actively on mac 1, clone music folder and mixxx library + prefs folder to mac 2 and use mixxx there as music player with tags, loops etc from mac 1.

Results in:
a) Mixxx on mac 2 thinks the music files are located at /Users/UsernameMac1/MusicFolder which of course is incorrect
b) sandbox dialog is shown
To fix this:
* Mixxx > Preferences > Library > Relink (process may never finish or get stuck)
* restart Mixxx
* rescan Library

Results in:
a) Library working again as expected
b) Sandbox warning no longer showing

The issues around wording and functionality of the sandbox dialog remain however. I am not sure if for my specific edge case, the sandbox dialog is expected or unexpected.

Also I do not know if when shown for correct cases it does what it is supposed to do or not.

Changed in mixxx:
importance: Undecided → Medium
status: New → Confirmed
assignee: nobody → Daniel Schürmann (daschuer)
milestone: none → 2.3.0
status: Confirmed → In Progress
Revision history for this message
Daniel Schürmann (daschuer) wrote :
Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

The remaining fixes are supposed to be done for 2.4.0 to prevent string changes and missing translations of these important instructions.

Changed in mixxx:
milestone: 2.3.0 → 2.4.0
status: In Progress → Confirmed
assignee: Daniel Schürmann (daschuer) → nobody
Revision history for this message
Daniel Schürmann (daschuer) wrote :
Changed in mixxx:
status: Confirmed → In Progress
assignee: nobody → Daniel Schürmann (daschuer)
Be (be.ing)
Changed in mixxx:
status: In Progress → Fix Committed
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10373

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.