Support generation of unsigned IPAs #5617
Comments
It seems like this issue might be related to code signing Have you seen our new Code Signing Troubleshooting Guide? It will help you resolve the most common code signing issues |
I assume the build environment has no signing identity in the keychain at all. Is that the case? Otherwise, it doesn't really matter how you sign the app initially, you can resign it afterwards, e.g. using |
@mgrebenets Correct, the idea is to have no signing identities involved at all until deployment, when But my issue is that fastlane actually makes it difficult to create an unsigned IPA for this purpose. It's still possible, via the workaround I mentioned above, but it would be cleaner to have an |
I haven't tried it myself yet, what happens if you pass I've looked through the source ( Adding new |
@mgrebenets That would indeed work, but the exporting half of gym sees a (blank) value for I did mention this in the original post, apologies if it wasn't clear. |
@richardszalay I can't figure out what your workaround is. I'm setting I would, by the way, be very much interested in this addition to gym. |
@jjochen Blog series incoming (when I can get around to finishing it) Are you passing anything at all as signing_identity to gym? The option needs to be absent. Failing that, what error are you seeing? Feel free to create a stack overflow question, or email me (firstname@firstnamelastname.com) |
I've finally published my blog series, which might give some context as to why I wanted to do this - https://blog.richardszalay.com/2016/08/22/ios-deploy-pipeline-1-introduction/ |
@richardszalay Awesome! Thanks so much for sharing. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem |
New Issue Checklist
Issue Description
I'd like to propose the addition of an "unsigned" option for gym.
tl;dr I'm happy to contribute the PR, which would simply add "CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY=''" to the archive command when the "unsigned"option is true
As for why it's needed: It's currently possible without a flag, but hoops need to be jumped. Namely, xcodebuild's archive command requires a SIGNING_IDENTITY value, even if it's blank. However, providing a "signing_identity" option as a blank string also causes it to trigger the "--signed" argument for the export command.
The feature could also be implemented by having the export archive command generator deal with blank signing_identity values, but I feel that an explicit option would better express intent.
Thoughts?
The text was updated successfully, but these errors were encountered: