9
xnight
6y

XCode you fucking piece of shit...

So I just wanted to process my ios app to the app store and start the archive process. All of the sudden:
Command CodeSign failed with a nonzero exit code

What? So there is an error and you cannot tell me the error code? All information you give me that it isn't zero!? Wow... Amazing... What a great user experience. Maybe it cannot resolve the error? Maybe it is some external tool Apple has no access to and that is the only valid error they can throw at us?

Oh hell no! It has something to do with the keychain access! But why tell the user? That wouldn't be as much fun as just tell it is a nonzero error, isn't it apple?!

In the end locking and unlocking my key chain solved the problem... Thanks for nothing XCode!

Comments
  • 0
    Welcome to programming... things that should make sense don't and cryptic error messages are part of our lives sadly
  • 1
    regardless of what Apple says, Xcode is clear indication that they treat programmers like second class citizens.

    They intentionally crash your app at runtime instead of forcing an alert at runtime.

    Then when you are in the debugger, they could have set it up so issuing an exception would display the message they wanted to tell you in their app-crashing communication language but NO... You have to go dig through the debug log output and find the fortune cookie text.

    The first time you get hit with this Apple fucktard approach it can take you a very long time to figure out why your app is crashing after there were no code modifications since the last time it ran cleanly.

    Apple engineers should not be allowed to breed as they undoubtedly make shitty abusive parents. Imagine being a kid and getting whacked on the back of the head so hard you slam to the floor and spending the rest of the day trying to figure out why by searching around the house for a clue.
Add Comment