How to solve "Could not load the Qt platform plugin "cocoa" in "" even though it was found."
-
HI, just guessing but maybe your app is picking up the QtDBus dylib from another place outside of your englauncher.app directory (and using relative paths).
To check, could you launch your app from the dist directory (i.e. where it runs successfully) and then open a Terminal and type
lsof -c englauncher
this will show what dlls/dylibs are loaded (and most importantly their paths). -
HI, just guessing but maybe your app is picking up the QtDBus dylib from another place outside of your englauncher.app directory (and using relative paths).
To check, could you launch your app from the dist directory (i.e. where it runs successfully) and then open a Terminal and type
lsof -c englauncher
this will show what dlls/dylibs are loaded (and most importantly their paths).@hskoglund, the process doesn't keep running, so not sure I can run lsof on it.
Another thing I tried is completely uninstalling python3 from brew repository, and reinstalling it directly from python3, using Mac disk image. Had to reinstall my pip libraries, and got the same exact issue.
I'm at my wits end with this, and think it's a Big Sur issue, though can't prove it.
-
Hi, one way stop your app from exiting, you could try showing a message box, for example like this:
... app = QApplication([]) alert = QMessageBox() alert.setText('Click me when lsof -c is done') alert.exec() ...then you should have time to do a
lsof -c englauncher -
Hi, one way stop your app from exiting, you could try showing a message box, for example like this:
... app = QApplication([]) alert = QMessageBox() alert.setText('Click me when lsof -c is done') alert.exec() ...then you should have time to do a
lsof -c englauncher@hskoglund, that didn't help, as it's not even able to load the Qt libraries. I even created a simple test app with your code, and while I can run it from ./dist/testapp, as soon as I copy it to /Applications, it fails loading the libraries in the same way.
-
Hi, please create a new forum post and describe your problem, what version of Python and MacOS you have etc.
@hskoglund ok,thank u
-
I fixed this on my machine by requiring py2app version 0.25
setup_requires=['py2app==0.25']
in the setup.pyThis problem is described in https://github.com/ronaldoussoren/py2app/issues/380 and there's already a patch. Just don't use 0.26 and 0.27.
