-
Notifications
You must be signed in to change notification settings - Fork 350
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
Encountering a code signing issue while building the .app #2783
Comments
Could you attach the other log files as well? There do not appear to be any relevant error messages in the build-tracer.log . |
@aibaars Do you need logs from git hub actions? |
Yes, and the ones from the debug artifact as well. |
@aibaars Hi, I created support ticket #3258270 and attached logs to it. |
@valeriiatym Thanks! I found the support ticket, but noticed you only uploaded two log files. I also didn't see the original error message you reported ( I did see quite a lot of error like |
yes, you are right. Updated ticket with logs. |
@valeriiatym The timestamps in the latest log does not match the ones from the previously uploaded files. This makes me think they are from different runs. It would be great to have a set of log files (actions logs, build-tracer.log, and any other log files in the debug artefact) of the same workflow run. Having a clear picture of what happens at which time hopefully give us enough information to diagnose what is going wrong. |
@aibaars yes, logs from gha workflow can be from different run. I re-run it several times with the same logic. And I can make you sure that nothing was changed. Thanks |
Hi,
We're still experiencing an issue with code signing when building the .app with the initialized CodeQL setup:
We've decided to run the CodeQL analysis on targets that do not require code signing. However, it would be ideal if you could address this issue so that we can run the analysis directly on the .app build.
Please refer to the attached log file for more details.
Thanks!
build-tracer.log
The text was updated successfully, but these errors were encountered: