-
Notifications
You must be signed in to change notification settings - Fork 47
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
Error uploading after updating to XCode 13 #27
Comments
I ran into the exactly same issue |
I am having the same problem, did anybody find a work around for this ? |
I ran into the exactly same issue |
Curious to know if anyone found a workaround for this or pinpointed the issue causing this? Is this happening randomly for everyone? |
I've been trying to use the task for a few days, but I end up with the same results as everyone else.
I end up with this authentication issue. So something must have changed for this process with the latest XCode version, but I'm having trouble finding what exactly. But this command-line fails only when ran on a github action agent. Locally on my dev machine it's working fine. So my guess is it has something to do with certificates ? |
Hey guys! I split this flow into two steps:
Example of the code:
|
thanks @VlasiukVV
worked like a charm |
Have the same error on XCode 13.4.1. |
Setting the environment variable
Such that you store your key as Which is described in the man page for altool:
|
I'm getting this error even though I can see my .p8 file in ~/private_keys
Is there something I need to change or do on my mac action runner machine?
Error message:
The file 'AuthKey_***.p8' could not be found in any of these locations: '~/actions-runner/_work/ProjectName/ProjectName/private_keys', '~/private_keys', '~/.private_keys', '~/.appstoreconnect/private_keys'.
Full output:
EDIT: I managed to upload the IPA manually from my mac. The IPA was saved correctly and altool accepted the upload when I did it through the terminal. However, when I try to use my Github Action for this, it always fails with this same error message.
I have included my workflow file here for context:
The text was updated successfully, but these errors were encountered: