MuseScore asks for access to contacts and calendar (Mac)
Twice now I have had MuseScore ask me for access to my contacts and calendar, seemingly without any reason. This is on the Mac.
I cannot reproduce the issue at will, but both times I was trying to access a file in the autosave folder.
The first time I was recovering from a crash and tried to save one of the open (autosaved) files.
The second time I was in the process of navigating to the autosave folder, in an attempt to recreate the issue. This was in the File/Open dialog. Suddenly, while I was navigating, the questions popped up.
I find it difficult to assign a severity ranking to the issue. No harm was done (hopefully) since I refused access. But the fact that it happened is rather disturbing for me. I do not think MuseScore is programmed to ask for these informations, but how can it then be that it does? It seems to me that something is very wrong here.
I would not raise an issue had it happened only once, but now it has happened a second time.
OS: macOS 10.14, Arch.: x86_64, MuseScore version (64-bit): 3.0.0.19967, revision: e482d05
Comments
I can only guess that somehow your OS is misinterpreting access to that folder as somehow being a request for contacts or calendar, as I cannot really think of anything MuseScore would be doing to trigger that on its own. Maybe some other app has laid claim over those folders and triggers a warning when anything else tries to horn in?
Anyhow, steps to reproduce the problem would be useful.
In reply to I can only guess that… by Marc Sabatella
I think you are right. I found reference to similar problems with the Atom app on Mojave. See https://github.com/atom/atom/issues/17687.
It may have to do with a new protection scheme in Mojave. Apparently, certain directory-related actions can trigger the behaviour. An excerpt from the source mentioned:
The MuseScore autosave files on Mojave are indeed kept in a folder sitting under ~/Library/Application Support.
Maybe it is easy to alter the logic so that no attempt is made to access sensitive files or folders. If not, since the impact is low, I would suggest to lay the issue to rest for now (but make a note in the documentation).
I got the same when trying to save a file that was in the autosave folder.