Rok Mandeljc
Rok Mandeljc
Hmmm, for starters, this build seems to have collected both `PyQt5` and `PyQt6` - it might not be the cause of the problem (it would be on Linux or macOS,...
> My first guess would be that this is caused by pinning of `PyQt6`, while `PyQt6-Qt6` is unpinned (and thus you get incompatible Qt libs from `PyQt6-Qt6` 6.6.1). https://github.com/dickreuter/Poker/actions/runs/7533127220/job/20505066214#step:5:161
If you add print statements, can you pinpoint where it crashes (for example, on what import)?
Can you reproduce it with a minimal example that performs just that call?
> The console gives some errors like block by system policy. There's your answer, then.
If you are 100% that symlinks are not the problem (you created your zip with `--symlinks` option), then either the other Mac is configured to not run untrusted (= unsigned)...
What is the output of `ls -l /Users/mac/Downloads/my-app/_internal`? And the output of `xattr -l /Users/mac/Downloads/my-app/_internal/Python`?
As well as: `codesign -vv /Users/mac/Downloads/my-app/_internal/Python`?
Does it work if instead of replacing the symlinks, you manually ad-hoc sign the `Python.framework` bundle? I.e., run `codesign -s - --deep --force /Users/mac/Downloads/my-app/_internal/Python.framework`?
I'm reopening this, as it is likely a regression from PyInstaller 5.x series. In v6, we preserve .framework bundle layouts (to address several other issues), but during the build, we...