See https://bugreports.qt.io/browse/QTBUG-73398?focusedCommentId=468111&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-468111 for lots of information. We probably should start updating our macOS build scripts now. One problem is that we cannot notarize (or sign) our jenkins builds.
Ivan, you're getting the short straw...
That's my specialty ;)
For the Jenkins builds: at least Catalina will allow some steps to allow running the executable. I can add those steps to a section in the manual. The problem will be after Catalina, it seems the idea is to not allow code not normalized to be run at all on future macOS versions.
Git commit 57312667861fcd84d7d00286c537d601bb1e0df4 by Ivan Yossi. Committed on 07/10/2019 at 12:55. Pushed by ivany into branch 'master'. Notarize macOS builds Add the necessary steps to create a notarized build for krita Notarize builds require a valid apple developer account. M +135 -20 packaging/macos/osxdeploy.sh https://invent.kde.org/kde/krita/commit/57312667861fcd84d7d00286c537d601bb1e0df4
Reopening since I haven't managed to get this to work yet.
*** Bug 413241 has been marked as a duplicate of this bug. ***
Now that we do notarize our builds, it turns out that native file dialogs still don't work...