Search results for

“codesign”

3,222 results found

Post

Replies

Boosts

Views

Activity

Reply to Mac app(ProcessMonitor) crashing with EXC_CRASH (Code Signature Invalid)
As a result of executing the command, the following results were obtained. My MacOS version is 10.15.5, but I'm worried that Runtime Varsion is 10.15.4. Is there any other place where you might have a problem? $ codesign -v -vvv /my.app/ - https://developer.apple.com/forums/content/attachment/dffe57a4-a2f6-45e0-81b3-a455c4842f3a $ codesign -d -vvv --entitlements :- /my.app/ - https://developer.apple.com/forums/content/attachment/4124f197-380d-48e3-9920-371ab7a5673f
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’20
Reply to Xcode 8 on 10.12 codesign segmentation fault
I got both issues with a fresh new certificate, so it was not just about the certificate being old.But I got around it by specifying the certificate by ID instead of name — first getting the ID via:security find-identity -p codesigningand, from the output of that, copying the long hex ID for the key I want, and pasting that into my codesign invocation:sudo codesign -s 001CA54450805B2D8D1646793D0339BA7EB931D1 --timestamp=none /opt/local/bin/ggdb
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Jan ’17
Reply to AppStore submission for Ruby/Glimmer app on MacOS without Xcode
To recap, my Ruby files for the app are located under ./app, with the gems being vendored. This library is located at ./app/vendor/bundle/ruby/3.3.0/gems/libui-0.1.2-arm64-darwin/vendor/libui.dylib. I'm curious if I should codesign the libui.dylib before building the binary with Tebako? If so, would I still need to codesign the Contents/Frameworks files under the app bundle? (I'm assuming yes on this latter point.) Thanks in advance for your suggestions.
Topic: Code Signing SubTopic: General
Apr ’25
Reply to Manually lipoing and codesigning
Ok, so it's been a while: I did get it to work! I grepped the codesign commands from the build output, wrote a script that, given two source .app directories, copies one of them to a new bundle, and then runs codesign on each of the bundles (including, at the end, the whole enclosing bundle). I also (cleverly, I think) extract the entitlements using codesign rather than using the ones from the project directory, and apply those. It seems to work! This is, I think, about the best I can do until and unless uSoft or MacPorts makes progress on their respective tools/environments. This is one of the reasons I always like being an OS engineer, so we don't have to (in general) rely on third party libraries/tools. Now I got a hankering to write a copyfile class in Swift.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jul ’22
Reply to codesigning with 2 user accounts on 1 machine
Hi again, We have now imported the p12 file into user B's login keychain via security import IDENTITY_FILE.p12 -k login.keychain After this, still the same behaviour: no identities listed from security find-identity -p codesigning and codesign still throws The specified item could not be found in the keychain. Reading your reply, I begin to wonder why user A stores it's identity within the system keychain instead of the login keychain. I can only state that codesigning works this way for user A. Following https://developer.apple.com/forums/thread/699268 , digital identities are listed in keyring within login / my certificates. This ist not the case for both users A and B, not in system and not in login. Mh ...
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Jul ’22
Reply to Extensions not opening if they are signed using the command line tools
AFAICT this is the command you’re using for signing: codesign -s Developer ID Application: XXXXXXXXX (XXXXXXX) -f --timestamp -o runtime --display --entitlements :- $i I see two oddities here: The -s tells it to sign code, but the --display tells it to display the code signature. I’m not sure what codesign does in that case, but it’s unlikely to be good. Remove the --display Your app and appex use entitlements, but --entitlements :- is telling codesign to display the entitlements, not apply them. You need to either: Apply the entitlements, using --entitlements /path/to/your.entitlements. Or preserve the entitlements, using --preserve-metadata=entitlements Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: General Tags:
Oct ’22
Reply to iOS manually built framework fails when installing app with Application Signature Not Valid
Hi Jeremy,My apologies for the delayed response.Here are the codesign outcomes (with associated commands):App:$ codesign -vvv /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app: valid on disk /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app: satisfies its Designated RequirementFramework in app:$ codesign -vvv /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app/Frameworks/Company.framework/ /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app/Frameworks/Company.framework/: valid on d
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jan ’16
Flutter iOS Widget Extension – CodeSign Failed (ActivityKit entitlement missing, cannot enable in Identifiers)
Hello everyone, I am developing a Flutter iOS application that includes a Widget Extension + Live Activity (ActivityKit). The project runs successfully on the iOS simulator when launched directly from Xcode, but it cannot be signed properly via Flutter and I cannot upload the build to App Store Connect due to the following CodeSign error: Command CodeSign failed with a nonzero exit code Provisioning profile … doesn't include the entitlement: com.apple.developer.activitykit.allow-third-party-activity This error never goes away no matter what I try. And the main problem is that my App ID does NOT show any ActivityKit or Live Activity capability in the Apple Developer portal → Identifiers → App ID. So I cannot enable it manually. However: Xcode requires this entitlement Flutter requires this entitlement When I add the entitlement manually in the .entitlements file, Xcode says: “This entitlement must be enabled in your Developer account. It cannot be added manually.” So I am stuck in a loop wher
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
1
0
383
Nov ’25
Reply to Stapling Error 65 (Applescript app)
And FYI, I've filed 50442691 …Oh, one tidbit about this bug: If you pass --deep to codesign, the notarisation should then succeed. Alternatively, and this is what I generally prefer, you can run codesign twice, once for document.wflow and again for the outer app. And yes, I realise that it’s still not following the rules as per TN2206 )-:Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: General Tags:
May ’19
Reply to Mac app(ProcessMonitor) crashing with EXC_CRASH (Code Signature Invalid)
As a result of executing the command, the following results were obtained. My MacOS version is 10.15.5, but I'm worried that Runtime Varsion is 10.15.4. Is there any other place where you might have a problem? $ codesign -v -vvv /my.app/ - https://developer.apple.com/forums/content/attachment/dffe57a4-a2f6-45e0-81b3-a455c4842f3a $ codesign -d -vvv --entitlements :- /my.app/ - https://developer.apple.com/forums/content/attachment/4124f197-380d-48e3-9920-371ab7a5673f
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’20
Reply to Xcode 8 on 10.12 codesign segmentation fault
I got both issues with a fresh new certificate, so it was not just about the certificate being old.But I got around it by specifying the certificate by ID instead of name — first getting the ID via:security find-identity -p codesigningand, from the output of that, copying the long hex ID for the key I want, and pasting that into my codesign invocation:sudo codesign -s 001CA54450805B2D8D1646793D0339BA7EB931D1 --timestamp=none /opt/local/bin/ggdb
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
Jan ’17
Reply to AppStore submission for Ruby/Glimmer app on MacOS without Xcode
To recap, my Ruby files for the app are located under ./app, with the gems being vendored. This library is located at ./app/vendor/bundle/ruby/3.3.0/gems/libui-0.1.2-arm64-darwin/vendor/libui.dylib. I'm curious if I should codesign the libui.dylib before building the binary with Tebako? If so, would I still need to codesign the Contents/Frameworks files under the app bundle? (I'm assuming yes on this latter point.) Thanks in advance for your suggestions.
Topic: Code Signing SubTopic: General
Replies
Boosts
Views
Activity
Apr ’25
Reply to Manually lipoing and codesigning
Ok, so it's been a while: I did get it to work! I grepped the codesign commands from the build output, wrote a script that, given two source .app directories, copies one of them to a new bundle, and then runs codesign on each of the bundles (including, at the end, the whole enclosing bundle). I also (cleverly, I think) extract the entitlements using codesign rather than using the ones from the project directory, and apply those. It seems to work! This is, I think, about the best I can do until and unless uSoft or MacPorts makes progress on their respective tools/environments. This is one of the reasons I always like being an OS engineer, so we don't have to (in general) rely on third party libraries/tools. Now I got a hankering to write a copyfile class in Swift.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Xcode Archive Failure: Code Signing Error with Hermes Framework
Error log invoking codesign: The error was related to the certificate, or rather its name, removing the quotes solved the problem
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Apr ’24
Reply to Code signature invalid on Mac OS X 10.10.x
Cause and solution: http://stackoverflow.com/questions/41865537/how-does-apples-codesign-utility-decide-which-sha-algorithms-to-sign-a-shared
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Feb ’17
Reply to codesigning with 2 user accounts on 1 machine
Hi again, We have now imported the p12 file into user B's login keychain via security import IDENTITY_FILE.p12 -k login.keychain After this, still the same behaviour: no identities listed from security find-identity -p codesigning and codesign still throws The specified item could not be found in the keychain. Reading your reply, I begin to wonder why user A stores it's identity within the system keychain instead of the login keychain. I can only state that codesigning works this way for user A. Following https://developer.apple.com/forums/thread/699268 , digital identities are listed in keyring within login / my certificates. This ist not the case for both users A and B, not in system and not in login. Mh ...
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Extensions not opening if they are signed using the command line tools
AFAICT this is the command you’re using for signing: codesign -s Developer ID Application: XXXXXXXXX (XXXXXXX) -f --timestamp -o runtime --display --entitlements :- $i I see two oddities here: The -s tells it to sign code, but the --display tells it to display the code signature. I’m not sure what codesign does in that case, but it’s unlikely to be good. Remove the --display Your app and appex use entitlements, but --entitlements :- is telling codesign to display the entitlements, not apply them. You need to either: Apply the entitlements, using --entitlements /path/to/your.entitlements. Or preserve the entitlements, using --preserve-metadata=entitlements Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’22
Reply to Cloudkit com.apple.developer.icloud-container-environment set to Production fails
I should add, even setting it to 'Development' causes it to not launch with a codesign error saying this entitlement is not allowed. WHY NOT!
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’15
Reply to Signing and uploading question of new version of an existing app.
With a current paid dev account, and Xcode set to auto codesign for that app, there shouldn't be a question here. Example is Xcode 11.4
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
Apr ’20
Command CodeSign failed with a nonzero exit code on build.
I get this error each time I try to build and can't figure it out. I've tried clearing derived data folder and restarting system.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
742
Activity
Oct ’22
Reply to iOS manually built framework fails when installing app with Application Signature Not Valid
Hi Jeremy,My apologies for the delayed response.Here are the codesign outcomes (with associated commands):App:$ codesign -vvv /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app: valid on disk /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app: satisfies its Designated RequirementFramework in app:$ codesign -vvv /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app/Frameworks/Company.framework/ /Users/indigo/Library/Developer/Xcode/DerivedData/LibraryTesting-azmocmdalqwlfochyihtxugfcdhs/Build/Products/Debug-iphoneos/LibraryTesting.app/Frameworks/Company.framework/: valid on d
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jan ’16
Flutter iOS Widget Extension – CodeSign Failed (ActivityKit entitlement missing, cannot enable in Identifiers)
Hello everyone, I am developing a Flutter iOS application that includes a Widget Extension + Live Activity (ActivityKit). The project runs successfully on the iOS simulator when launched directly from Xcode, but it cannot be signed properly via Flutter and I cannot upload the build to App Store Connect due to the following CodeSign error: Command CodeSign failed with a nonzero exit code Provisioning profile … doesn't include the entitlement: com.apple.developer.activitykit.allow-third-party-activity This error never goes away no matter what I try. And the main problem is that my App ID does NOT show any ActivityKit or Live Activity capability in the Apple Developer portal → Identifiers → App ID. So I cannot enable it manually. However: Xcode requires this entitlement Flutter requires this entitlement When I add the entitlement manually in the .entitlements file, Xcode says: “This entitlement must be enabled in your Developer account. It cannot be added manually.” So I am stuck in a loop wher
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
1
Boosts
0
Views
383
Activity
Nov ’25
Reply to Stapling Error 65 (Applescript app)
And FYI, I've filed 50442691 …Oh, one tidbit about this bug: If you pass --deep to codesign, the notarisation should then succeed. Alternatively, and this is what I generally prefer, you can run codesign twice, once for document.wflow and again for the outer app. And yes, I realise that it’s still not following the rules as per TN2206 )-:Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’19
Reply to April 2020 requirement
One more thing. Do I understand correctly, that it will be checked by moderators during submitting to AppStore? If I use enterprise codesign I am able to skip this restriction?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Aug ’19