search

DanTheMan827 / ios-app-signer

This is an app for OS X that can (re)sign apps and bundle them into ipa files that are ready to be installed on an iOS device.
https://dantheman827.github.io/ios-app-signer
GNU General Public License v3.0
5.64k stars 1.06k forks source link

Quick workaround for macOS Sierra bug not showing provisioning profiles #20

Closed NoahSaso closed 8 years ago

NoahSaso commented 8 years ago

This is just a fix for the macOS Sierra bug people are experiencing (https://github.com/DanTheMan827/ios-app-signer/issues/19). /usr/bin/security is a bit different and gives an extra line of error message before the xml is outputted. I just went ahead and removed this line and passed the xml along to the rest of the code so it works :)

bradleyduncan commented 8 years ago

Gunna test this now. Thank you for your contribution to the topic!!! Testing... Building

bradleyduncan commented 8 years ago

Thank you so much for this mate! Confirmed to be working!

bradleyduncan commented 8 years ago

https://mega.nz/#!4oAjzQjA This is the built version to anyone struggling to build the app in Xcode.

KnowhereFern commented 8 years ago

Thanks bradleyduncan. Can you share the passcode/decryption key for the mega upload file?

DanTheMan827 commented 8 years ago

@NoahSaso Thanks, I haven't gotten around to installing Sierra on my hackintosh and my real Mac is "too old"...

What is the actual output of the security command when given the provisioning profile?

NoahSaso commented 8 years ago

@DanTheMan827 It's actually pretty strange because I read the security cms command help and all the arguments you use are valid. Anyways, the output is: security: SecPolicySetValue: One or more parameters passed to a function were not valid. *all the valid xml* I just take out that first line if I find it in the output, probably the wrong way to do it but it works for now.

bradleyduncan commented 8 years ago

https://mega.nz/#!4oAjzQjA!est5RfNBhzJlMh1kXADbfC6_BxZJbEDSyj1kgoaC8Dk

NoahSaso commented 8 years ago

@DanTheMan827 I'm reading around and beginning to think this actually isn't a user problem. I'm staring at the man pages and looking at the terminal help options, and I just keep being reassured that the two arguments you use are completely valid. Maybe it's an internal macOS Sierra problem... I think you honestly just have to hack your way around it like I did, since it does output the correct XML anyways.