Unsolved QtWebEngineProcess OSX codesign issues
zambiatall last edited by
I tried to sign and notarize example application "simplebrowser" from Qt5.12.7 examples.
If I sign the main application: simplebrowser.app/Contents/MacOS/simplebrowser with deep and runtime options It works perfect, but I cannot notarize this bundle because I have to sign simplebrowser.app/Contents/Frameworks/QtWebEngineCore.framework/Helpers/QtWebEngineProcess.app/Contents/MacOS/QtWebEngineProcess too. If I make this, I can notarize the application. But the program does not work on websites with Java Script.
Also I tried this solution: https://forum.qt.io/topic/102212/qtwebengine-signing-issues It does not work
I got the same propblem...
@zambiatall said in QtWebEngineProcess OSX codesign issues:
But the program does not work on websites with Java Script.
I am having the same issue...but not with the simplebrowser sample. It's occurring in a real app that has been functioning fine up until OSX10.14.x. The app in question works on OSX10.13.x and has been compiled with Qt5.12.7. It also worked on all previous versions of Qt using QWebEngine.
My app can load webpages that reside on the local file system (file:) but when accessing a webpage on another url that contains Java Script, a blank page is displayed. The loadStarted, loadProgress, and urlChanged events all fire, but the loadFinished event never does.
I have not tried the "notarization fix" outlined here..
..but the app has been successfully notarized by Apple.
For me it was a QtWebEngineProcess entitlement and signing issue.