3.5RC -- Blank upload dialog on Mac (see details)

• Jul 25, 2020 - 17:42
Reported version
S2 - Critical

Invoke "Save Online" from 3.5RC on Mac (Catalina 10.15.6). Second (large) dialog comes up empty.


In reply to by ABL

I cannot figure out from that if the poster finally succeeded. Are there Qt support tickets? One would think that if the Qt Web Engine couldn't be made to work with Catalina, people would be in a state of alarm. If that is the case, of course, there is always reversion to the status quo ante, "ignore the malware warning'. Upload to Web can't fail.

In principle, at that link they give a possible solution for the notarization problem of QtWebEngine, to be run at packaging time (while digitally signing the app). The symptoms of their problem look suspicoiusly similar to our problem, so I think their solution could solve also this issue, but I couldn't verify it (yet).

In reply to by ABL

Setting up the Mac build environment is an arduous chore; I've been there. I'd rather someone else who has this already set up, and has dealt with this kind of issue before, did so. I fear I don't have the Qt or Mac-signing knowledge to take this upon my own shoulders right now.

See proposed PR https://github.com/musescore/MuseScore/pull/6378
A test executable can be found here:
or here if you don't have a Github account: https://drive.google.com/file/d/1D4CErEhEBWKCRHIaem3na1qwRDe-mDaN/view?…
In order to run it, you should unblock it by running:
xattr -cr /Applications/MuseScoreNightly.app

[I am not yet switching the status to PR created since it is still a work in progress]

@BSG : Thank you very much for the test.
Just to be sure that it is really that change that solves the bug: could you please use the (sudo) xattr -cr also on MuseScore 3.5RC and see if the upload dialog is still blank?
[By the way, the build is flagged as a nightly build, so it searches for saved preferences in a different folder than the builds with the release flag. It is normal behavior that it couldn't find the saved credentials.]
Thank you again for your help.

Status active PR created

Ok. Thank you :-)
So the PR should be the right solution. I will also update the PR message on Github.

Fix version