New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[6.0, MacOS] Chromium.app/Contents/MacOS/Chromium: bundle format unrecognized, invalid, or unsuitable #7969
Comments
Huh... so This might have worked in v5 (if you are willing to ignore part where the 300 MB I suppose we will have to extend the .framework bundle handling code to .app bundles as well. And the binary processing code (signing in particular) will need to be revised to explicitly handling .framework and .app bundles; i.e., copy all their contents, and only then attempt a (re)sign - I suspect that is the case why this is blowing up now; we copy only the binary in question to bincache for path rewriting and (re)signing, and it then fails because for example I'm marking this as a bug, although the scope probably makes it more of a feature. |
+1 |
@benjie-git How do you include that .app bundle in the PyInstaller app? It is presumably smuggled in as data (otherwise I think v5 would also raise an error), but do you use |
Thanks! In my spec file, I use a data parameter in my Analysis() call that adds a directory containing my sub-app to the build, like this:
During my build process, conainerDir contains my SubApp.app bundle. I am then even able to run code signing on the subapp, and then on the full app, and everything works smoothly for distribution as a trusted app on MacOS. FYI, my subapp is also built using PyInstaller, earlier in my build process. |
Description of the issue
Context information (for bug reports)
Output of
pyinstaller --version
:6.0.0
(v5.13.2 works)Version of Python: v3.11.5
Platform: macOS-12.7-x86_64-i386-64bit
How you installed Python: pyenv
Did you also try this on another platform? Does it work there?: Yep it works on Liniux/Windows platform.
try the latest development version, using the following command: Likewise - it doesn't work
follow all the instructions in our "If Things Go Wrong" Guide
(https://github.com/pyinstaller/pyinstaller/wiki/If-Things-Go-Wrong) and
Make sure everything is packaged correctly
--noupx
or setupx=False
in your .spec-file--debug
topyi-makespec
orpyinstaller
or useEXE(..., debug=1, ...)
in your .spec file.A minimal example program which shows the error
# workon into virtualenv $ pip install playwright $ PLAYWRIGHT_BROWSERS_PATH=0 python -m playwright install chromium
Stacktrace / full error message
Please also see https://github.com/pyinstaller/pyinstaller/wiki/How-to-Report-Bugs
for more about what would use to solve the issue.
The text was updated successfully, but these errors were encountered: