Anybody else having trouble code-signing?

  • I try to build my app and get "The timestamp was not trusted.Command /usr/bin/codesign failed with exit code 1".

    I built the same app many times yesterday with no problem, and I haven't changed anything.

    I see on devforums that others have started seeing this.  Anybody here know what's going on?  I'm trying to codesign with Developer ID, in case that matters.

    --Andy
  • On Fri, 7 Jun 2013 15:32:46 +0000, Andy Lee said:

    > I try to build my app and get "The timestamp was not trusted.Command /
    > usr/bin/codesign failed with exit code 1".
    >
    > I built the same app many times yesterday with no problem, and I haven't
    > changed anything.
    >
    > I see on devforums that others have started seeing this.  Anybody here
    > know what's going on?  I'm trying to codesign with Developer ID, in case
    > that matters.

    Our buildbot had a similar problem last night, with an CSSMERR_TP_NOT_TRUSTED error.  (God forbid we might want to release today's build, without blessing from the mother ship!)

    Cheers,

    --
    ____________________________________________________________
    Sean McBride, B. Eng                <sean...>
    Rogue Research                        www.rogue-research.com
    Mac Software Developer              Montréal, Québec, Canada
  • I've had this as well. I think it is a problem with Apple's timeserver that they use for codesigning.

    This has been my first go at getting code signing to work and it added an extra layer of confusion for someone who is clueless as to how it all works.

    Kevin
    On 7 Jun 2013, at 16:32, Andy Lee <aglee...> wrote:

    > I try to build my app and get "The timestamp was not trusted.Command /usr/bin/codesign failed with exit code 1".
    >
    > I built the same app many times yesterday with no problem, and I haven't changed anything.
    >
    > I see on devforums that others have started seeing this.  Anybody here know what's going on?  I'm trying to codesign with Developer ID, in case that matters.
    >
    > --Andy
    >
    > _______________________________________________
    > Do not post admin requests to the list. They will be ignored.
    > Xcode-users mailing list      (<Xcode-users...>)
    > Help/Unsubscribe/Update your Subscription:
    > https://lists.apple.com/mailman/options/xcode-users/<ktam...>
    >
    > This email sent to <ktam...>
  • On 7 Jun 2013, at 16:46, Sean McBride <sean...> wrote:

    > Our buildbot had a similar problem last night, with an CSSMERR_TP_NOT_TRUSTED error.  (God forbid we might want to release today's build, without blessing from the mother ship!)

    I got this error when trying to archive and I assumed I got something wrong with my distribution certificate without knowing what.

    Actually I haven't been able to determine whether there is a more sensible way to distribute an app that you are not releasing via the apple store beyond getting the app code signed, zipping it and then making it available.

    Kevin
  • On Friday, June 7, 2013, Sean McBride <sean...> wrote:

    > Our buildbot had a similar problem last night, with an
    > CSSMERR_TP_NOT_TRUSTED error.  (God forbid we might want to
    > release today's build, without blessing from the mother ship!)

    This is still occurring (and isn't just happening to you). Right
    now it looks like an infrastructure problem. I've seen
    suggestions that --timestamp=none may work around it temporarily
    (although the current symptoms are different from timestamp
    server failures in the past).

    R.
    --
    Rich Siegel                                Bare Bones Software, Inc.
    <siegel...>                      <http://www.barebones.com/>

    Someday I'll look back on all this and laugh... until they
    sedate me.
  • On Friday, June 7, 2013, Andy Lee <aglee...> wrote:

    > I try to build my app and get "The timestamp was not
    > trusted.Command /usr/bin/codesign failed with exit code 1".

    I didn't get a timestamp error (Xcode 4.6.2), I got something
    far more opaque.

    In any event, *temporarily* adding "--timestamp=none" to your
    Code Signing Flags build setting will work around the outage and
    let you build, until the server comes back up. (You don't want
    to ship this way, it's just a temporary workaround.)

    R.
    --
    Rich Siegel                                Bare Bones Software, Inc.
    <siegel...>                      <http://www.barebones.com/>

    Someday I'll look back on all this and laugh... until they
    sedate me.
  • Hi Andy

    I had this kind of problem when I stopped syncing my computer with Apple's
    timer server, as I was behind a firewall that prevented it (it only
    allowed http at port 80 for security reasons). The moment I synced the
    time of the computer the problem went away. I think this problem is a
    symptom from Apple's effort to prevent hackers from messing with the
    Developer ID validity.

    HTH

    João

    On 6/7/13 5:50 PM, "<xcode-users-request...>"
    <xcode-users-request...> wrote:

    > Message: 1
    > Date: Fri, 07 Jun 2013 15:32:46 +0000 (GMT)
    > From: Andy Lee <aglee...>
    > To: Xcode Users <xcode-users...>
    > Subject: Anybody else having trouble code-signing?
    > Message-ID: <ff72513b-17c3-4c61-8333-521f37ac567e...>
    > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
    >
    > I try to build my app and get "The timestamp was not trusted.Command
    > /usr/bin/codesign failed with exit code 1".
    >
    > I built the same app many times yesterday with no problem, and I haven't
    > changed anything.
    >
    > I see on devforums that others have started seeing this.  Anybody here
    > know what's going on?  I'm trying to codesign with Developer ID, in case
    > that matters.
    >
    > --Andy
  • On Jun 7, 2013, at 12:18 PM, Rich Siegel <siegel...> wrote:
    > On Friday, June 7, 2013, Andy Lee <aglee...> wrote:
    >
    >> I try to build my app and get "The timestamp was not trusted.Command /usr/bin/codesign failed with exit code 1".
    >
    > I didn't get a timestamp error (Xcode 4.6.2), I got something far more opaque.
    >
    > In any event, *temporarily* adding "--timestamp=none" to your Code Signing Flags build setting will work around the outage and let you build, until the server comes back up. (You don't want to ship this way, it's just a temporary workaround.)

    Thanks, everybody.  To my great relief, Apple has fixed whatever the problem was.

    Now if only devforums wasn't down I could thank the people there who chimed in too...

    --Andy
  • On 2013 Jun 07, at 12:44, João Varela <joaocvarela...> wrote:

    > I think this problem is a symptom from Apple's effort to prevent hackers from messing with the
    > Developer ID validity.

    Yes, it is.

    http://lists.apple.com/archives/apple-cdsa/2013/Mar/msg00018.html

    The author of that post, Perry the Cynic, is an Apple engineer.
previous month june 2013 next month
MTWTFSS
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
Go to today