10-13-2019, 06:09 PM
10-13-2019, 08:09 PM
You can use the script I linked above (you need a valid apple developer account). But you don't have to notarise it again yourself, it's enough to send it one time to Apple.
The correct url to the script is: https://github.com/HandBrake/HandBrake/blob/master/macosx/hbnotarize
The correct url to the script is: https://github.com/HandBrake/HandBrake/blob/master/macosx/hbnotarize
10-15-2019, 03:17 AM
Can't you just right click → Open to bypass app signing and thus notarization?
If that doesn't work anymore, you should be able to just turn off Gatekeeper. Enter in the Terminal:
If you like Gatekeeper, you can turn it back on after running Dolphin once, with:
If that doesn't work anymore, you should be able to just turn off Gatekeeper. Enter in the Terminal:
Code:
sudo spctl --master-disableIf you like Gatekeeper, you can turn it back on after running Dolphin once, with:
Code:
sudo spctl --master-enable10-16-2019, 06:28 PM
Is Dolphin now working with Catalina macOS ? Or do I still have to follow this instruction right here in this page?
10-19-2019, 06:14 PM
Anybody?
10-27-2019, 11:59 PM
I waited patiently for 8 days. Nobody wants to share the information about Catalina macOS working with Dolphin ?
10-28-2019, 07:03 AM
If you cared to read the second post, you would already have an answer
(10-10-2019, 06:04 AM)MayImilae Wrote: [ -> ]...if you install Catalina, Dolphin will work today, thanks to Apple putting off the notarization requirement at the last minute. But in three months or however long it is and the notarization requirement kicks in... we don't know. Apple has been very very opaque in this whole process. Will we be able to run as though Dolphin is unsigned? Will it cause a conflict and we'll have to remove our digital signature so only new builds after that point will work? Will unsigned apps even work at all? Seriously, their messaging could not be more messy and confusing.
[...]
Basically, we just don't know anything. Dolphin will run on Catalina today, but tomorrow... ┐(´-｀)┌
10-28-2019, 08:08 AM
If you really want to upgrade to Catalina, upgrade to Catalina. Dolphin is only one of many applications that one needs to consider when upgrading, after all, and if all your other variables are leaning toward upgrade, then just do it. Even in the absolute worst case scenario and we are forced to drop macOS as a platform, you just use bootcamp to run Dolphin on Windows; which you probably should be doing anyway since the graphics API situation is terrible on macOS! But if you care enough about Dolphin support on macOS itself for it to determine whether you upgrade or not, then absolutely, do not upgrade until the notarizing situation has stabilized. That will be at least January 2020, but it could be even further in the future. And well, that's just the situation right now. I don't have any more information for you, there just isn't any.
Spoiler: (Show Spoiler)
For me, 10.16 is the big question mark. Will they clamp down on gatekeeper and make it harder to run unsigned and/or unnotarized apps, as the rumors say? Or will 10.16 see Apple responding to what happened with 10.15 and working to keep macOS open? As a macOS user, personally I'm going to firmly stay on 10.14 until I see what 10.16 does. Things are changing, and macOS 10.15 is but a transition step. Only when more of that change has progressed will we have a decent idea of where Apple is taking macOS.
10-28-2019, 07:56 PM
Thank you very much for your replying. I appreciate it. That's all I need to know. Have a good day. And good morning to you all from Portugal.
10-29-2019, 06:31 PM
You misunderstood how notarization works: all signed apps on 10.15 (and 10.14.5) already needs to be notarized. The only concession Apple made is that you don't need the hardened runtime right now to notarise an app.
If you can't notarise it (and it's not hard to do but I don't know how your build system works) you should stop signing Dolphin for macOS and distribuite it unsigned.
Right now your development versions available on the download page can't run on 10.14 or 10.15, because they are not properly signed (only signed but not notarized).
If you can't notarise it (and it's not hard to do but I don't know how your build system works) you should stop signing Dolphin for macOS and distribuite it unsigned.
Right now your development versions available on the download page can't run on 10.14 or 10.15, because they are not properly signed (only signed but not notarized).