[GH-ISSUE #58] Error: Process completed with exit code 1 #36

Closed
opened 2026-03-04 00:23:19 +03:00 by kerem · 11 comments
Owner

Originally created by @isibizi on GitHub (May 25, 2021).
Original GitHub issue: https://github.com/SignTools/SignTools/issues/58

Hello, i have an dev accout but i cant sign my apps

What is the problem?

Run ./sign.sh
Obtaining files...
Creating keychain...
Importing certificate...
1.2.840.113635.100.1.61
Signing...
Usage: xresign.sh -i APP_PATH -c CERT_NAME [-epbdas ...]

-i path to input app to sign
-c Common Name of signing certificate in Keychain
-e new entitlements to use for app (Optional)
-p path to mobile provisioning file (Optional)
-b new bundle id (Optional)
-d enable app debugging (get-task-allow) (Optional)
-a force enable support for all devices (Optional)
-s force enable file sharing through iTunes (Optional)
-n set bundle id to mobile provisioning app id (Optional)
-w write bundle id to file (Optional)
Error: Process completed with exit code 1.

Originally created by @isibizi on GitHub (May 25, 2021). Original GitHub issue: https://github.com/SignTools/SignTools/issues/58 Hello, i have an dev accout but i cant sign my apps What is the problem? Run ./sign.sh Obtaining files... Creating keychain... Importing certificate... 1.2.840.113635.100.1.61 Signing... Usage: xresign.sh -i APP_PATH -c CERT_NAME [-epbdas ...] -i path to input app to sign -c Common Name of signing certificate in Keychain -e new entitlements to use for app (Optional) -p path to mobile provisioning file (Optional) -b new bundle id (Optional) -d enable app debugging (get-task-allow) (Optional) -a force enable support for all devices (Optional) -s force enable file sharing through iTunes (Optional) -n set bundle id to mobile provisioning app id (Optional) -w write bundle id to file (Optional) **Error: Process completed with exit code 1.**
kerem 2026-03-04 00:23:19 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@ViRb3 commented on GitHub (May 25, 2021):

Hello. What type of signing profile did you use? Provisioning profile or account username and password? How did you deploy the service? Heroku? The error probably means that something was left empty. Feel free to join the Discord if you want faster support: https://discord.gg/A4T6npnRCk

<!-- gh-comment-id:847811700 --> @ViRb3 commented on GitHub (May 25, 2021): Hello. What type of signing profile did you use? Provisioning profile or account username and password? How did you deploy the service? Heroku? The error probably means that something was left empty. Feel free to join the Discord if you want faster support: https://discord.gg/A4T6npnRCk
Author
Owner

@isibizi commented on GitHub (May 25, 2021):

I have used a prov.profile and a p12 cert from an paid dev account. I have used heroku to deploy the service.

<!-- gh-comment-id:847817212 --> @isibizi commented on GitHub (May 25, 2021): I have used a prov.profile and a p12 cert from an paid dev account. I have used heroku to deploy the service.
Author
Owner

@ViRb3 commented on GitHub (May 25, 2021):

Thanks a lot for the report. The error is almost certainly that the signer cannot find any valid code signing certificate inside your cert.p12. I updated the code to show more helpful error messages, you will have to re-create your ios-signer-ci to get the new changes. To fix your problem, we will discuss over Discord. I will update this issue with a summary once we are done.

<!-- gh-comment-id:847917956 --> @ViRb3 commented on GitHub (May 25, 2021): Thanks a lot for the report. The error is almost certainly that the signer cannot find any valid code signing certificate inside your `cert.p12`. I updated the code to show more helpful error messages, you will have to re-create your `ios-signer-ci` to get the new changes. To fix your problem, we will discuss over Discord. I will update this issue with a summary once we are done.
Author
Owner

@ViRb3 commented on GitHub (Jun 2, 2021):

Please try the latest version, it includes a lot of improvements everywhere. Don't forget to update your ios-signer-ci as well if applicable.

<!-- gh-comment-id:852819646 --> @ViRb3 commented on GitHub (Jun 2, 2021): Please try the latest version, it includes a lot of improvements everywhere. Don't forget to update your ios-signer-ci as well if applicable.
Author
Owner

@isibizi commented on GitHub (Jun 2, 2021):

The workflow is not running anymore

This workflow has a workflow_dispatch event trigger.

I have try too removed the repo and use the template again with the same workflow error

<!-- gh-comment-id:852868618 --> @isibizi commented on GitHub (Jun 2, 2021): The workflow is not running anymore `This workflow has a workflow_dispatch event trigger.` I have try too removed the repo and use the template again with the same workflow error
Author
Owner

@ViRb3 commented on GitHub (Jun 2, 2021):

Where do you get the error?

<!-- gh-comment-id:852872172 --> @ViRb3 commented on GitHub (Jun 2, 2021): Where do you get the error?
Author
Owner

@isibizi commented on GitHub (Jun 2, 2021):

I have the error in github under my repo in "actions"

https://ibb.co/tmrjtF5

<!-- gh-comment-id:852881009 --> @isibizi commented on GitHub (Jun 2, 2021): I have the error in github under my repo in "actions" https://ibb.co/tmrjtF5
Author
Owner

@ViRb3 commented on GitHub (Jun 2, 2021):

That is not an error. It simply means that no signing jobs have been run yet.

<!-- gh-comment-id:852881871 --> @ViRb3 commented on GitHub (Jun 2, 2021): That is not an error. It simply means that no signing jobs have been run yet.
Author
Owner

@isibizi commented on GitHub (Jun 2, 2021):

i have uploaded the ipa and the workflow runs very late ~5 min after ther upload is finshed. i dont know is this a prob of heroku or you tool ?

<!-- gh-comment-id:852885553 --> @isibizi commented on GitHub (Jun 2, 2021): i have uploaded the ipa and the workflow runs very late ~5 min after ther upload is finshed. i dont know is this a prob of heroku or you tool ?
Author
Owner

@ViRb3 commented on GitHub (Jun 2, 2021):

Most likely Github Actions is overloaded, so it takes a while to pick up your job. It happens sometimes. Let me know if the issue persists for more than a day and I'll look into it.

<!-- gh-comment-id:852886975 --> @ViRb3 commented on GitHub (Jun 2, 2021): Most likely Github Actions is overloaded, so it takes a while to pick up your job. It happens sometimes. Let me know if the issue persists for more than a day and I'll look into it.
Author
Owner

@ViRb3 commented on GitHub (Jun 5, 2021):

Assuming fixed, feel free to comment and I will re-open.

<!-- gh-comment-id:855292508 --> @ViRb3 commented on GitHub (Jun 5, 2021): Assuming fixed, feel free to comment and I will re-open.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SignTools#36
No description provided.