petiatil

Results 17 comments of petiatil

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

@rokm Minor update: I can confirm that the basic "hello world" application works, and I do (re)sign every binary. Thank you for your help. I've narrowed the issue to an...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

Shortly after my initial post, I updated it to display my "Main app entitlements" rather than just the 'inherit' entitlements. To be clear, I've continued to use both the 'allow-jit'...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

To conclude my previous comment: - I'll proceed to test with an app bundle. Unless advised differently, I'll start with version 5.13.2. - My current assumption is that "additional-hooks" might...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

Results from testing with an app bundle: In the codesigning phase, an error occurs, which may or may not relate to the main issue: ''' 1376 INFO: PyInstaller: 6.1.0 1376...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

### **.DS_Store locations:** app_name.app/Contents/Resources/pyphen app_name.app/Contents/Resources/nltk_data/tokenizers/punkt app_name.app/Contents/Resources/speechbrain app_name.app/Contents/Resources/nltk app_name.app/Contents/Resources/torch app_name.app/Contents/Resources/torch/include app_name.app/Contents/Resources/torch/include/torch/csrc app_name.app/Contents/Resources/torch/include/torch/csrc/jit app_name.app/Contents/Resources/torch/include/ATen app_name.app/Contents/Resources/torch/utils app_name.app/Contents/Resources/torch/share/cmake app_name.app/Contents/Resources/sklearn app_name.app/Contents/Resources/transformers app_name.app/Contents/Resources/numba app_name.app/Contents/Frameworks/torch app_name.app/Contents/Frameworks/sklearn app_name.app/Contents/Frameworks/numba ### **Python environment** I created my virtual Python environment using...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

### **The temporary elements** I'm pleased to report (in hopes that the issue is much simpler than first deemed) that 'hanging at the `whisperx` import' was incidental. It just happened...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

Good points to reflect on, thank you. To clarify (if I understand upon further reflection), and to your point on the hello-world app, I don't believe the problem is inherent...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

> Since you are using --force, you are replacing any pre-existing signatures with your own, so there should be no divergence/discrepancy. Good reminder, I would just maintain skepticism with respect...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

(Message 2) Quick update: I'm not certain, but (answering my own question) it may be crucial to place the executable in Executables rather than the default Resources in the Copy...

Using codesigning flags still results in "no cdhash, completely unsigned?" errors (with --onedir executable or app bundle executable)

**Notes on current results** (specifics in attached image, if useful). After testing with adding the app bundle to Executables, the result is the same. **Note:** The first thing that occurs...