Code signing issue: "obsolete resource envelope"

Question

Created Jun ’15

Replies 4

Boosts 0

Views 3.8k

Participants 3

Hi all,

I have a Developer ID app (that is not sandboxed), which I have built, archived & exported for Developer ID successfully many times. When I tried to archive & export the latest version, then check the resulting app via

spctl --verbose=4 --assess --type execute /path/to/my.app

I am getting the error:

rejected
source=obsolete resource envelope

I can't figure out what has changed, and how to diagnose it or fix it. The app has many bundles and helpers, all of which appear to be signed when exporting. I am building on 10.10.3 using Xcode 6.3.2.

Building, archiving & exporting another Developer ID app works correctly, so it seems like it must be something specific to that first app.

Any clues?

Boost

Answer 1

DTS Engineer OP

Apple

Jun ’15

It sounds like your app, or part of it, has a version 1 code signature. This issue is discussed in depth in TN2206 OS X Code Signing In Depth.

Share and Enjoy
—
Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 2

Dejal OP

Jun ’15

Thanks for the reply.

It turned out that one of the frameworks included in the app (Growl) was the cause. I traced it by using spctl to look at each bundle and framework in turn till it reported an error (sidenote: having it report the specific executable that caused it when looking at the whole app would have been helpful).

I solved it by manually codesigning the framework with my Developer ID. I had thought that doing the export from the archive would re-code-sign everything correctly, but apparently not.

0

Answer 3

fzwo OP

Jul ’15

EDIT: Turns out it was an entirely different issue, or a compound of multiple issues. Nothing at all to do with ElCap or Xcode 7.

0

Answer 4

DTS Engineer OP

Apple

Jul ’15

(sidenote: having it report the specific executable that caused it when looking at the whole app would have been helpful).

Please do file a bug about the lack of diagnostics here, posting your bug number here, just for the record.

Share and Enjoy
—
Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

0