Search results for

codesign

3,114 results found

Post

Replies

Boosts

Views

Activity

Reply to GateKeeper rejects my app in 10.11.4, which was working fine until 10.11.3
This is performed on OSX 10.11.6 (the bundle was signed on Yosemite):codesign -dvvv --deep /Users/Giel/Desktop/MyApp.appExecutable=/Users/Giel/Desktop/MyApp.app/Contents/MacOS/MyApp2Identifier=com.x.xFormat=bundle with Mach-O thin (i386)CodeDirectory v=20200 size=41941 flags=0x0(none) hashes=2089+3 location=embeddedHash type=sha1 size=20CandidateCDHash sha1=6d5d39082c55f2bb3257a5eb4d71ef3be6e6a686Hash choices=sha1CDHash=6d5d39082c55f2bb3257a5eb4d71ef3be6e6a686Signature size=8512Authority=Developer ID Application: my nameAuthority=Developer ID Certification AuthorityAuthority=Apple Root CATimestamp=09 Jun 2016 22:35:26Info.plist entries=15TeamIdentifier=xSealed Resources version=2 rules=12 files=318Nested=MacOS/libcgunwind.1.0.dylibInternal requirements count=1 size=200Then I tried to sign it again in El Cap, which led to the ‘rejectedsource=obsolete resource envelope’ error. Now I get this:codesign -dvvv --deep /Users/Giel/Desktop/MyApp.appExecutable=/Users/Giel/Desktop/MyApp.app/Contents/MacOS/MyApp
Topic: Privacy & Security SubTopic: General Tags:
Jun ’16
Build ios app for device on sierra
I try to build ios app for device on sierra but I met build error as below.error: A cryptographic verification failure has occurred. *** error: Couldn't codesign /Users/***/Library/Developer/Xcode/DerivedData/CodeSignSample-bddhnjftgqciphgglvvnffjcngxi/Build/Products/Debug-iphoneos/CodeSignSample.app/Frameworks/libswiftCore.dylib: codesign failed with exit code 1Is any solution?
20
0
3.3k
Jun ’16
Codesigning Error
Even when I start a new project from XCode 8 & macOS 10.12 and try to test it on the device, I get this codesigning error :error: A cryptographic verification failure has occurred.I tried removing my developer account from XCode, and even revoked all my certificates and provisionning profiles on the Member Center, but I still get this error.Am I the only one ?
9
0
1.8k
Jun ’16
What's New in Security Notes
Lucia Ballard - Secure Transports Engineering ManagerSimon Cooper - Trusted Execution Engineering ManagerNetwork Security on iOSCryptography APIsPlatform security on macOSSecure Communications (iOS)HTTPS is the new HTTP- Confidentiality- Data integrity- Not all HTTPS is created equal.Current standards:For NSURLSession and NSURLConnection APIs- Use TLSv1.2- Strong crypto - AES-128 and certificates signed with SHA-2- Forward secrecy - ECDHEExceptions - global or for particular domainsApp Transport Security EnforcementEnforced at the end of 2016 for MAS appsReasonable justification required for most exceptionsExample - communicating with a specific third-party service, which isn't (yet) compliant.New exceptions to make it easier:- Streaming media using AVFoundation- Web content exception using WKWebViewWatch video for plist key to use for WKWebView.RC4 now disabled by defaultSSLv3 disabled in Secure TransportOther algorithms are starting to show their age and are being deprecated:- SHA-1- 3DESNow is the time to
0
0
1.3k
Jun ’16
System application fails codesign verification on OSX 10.11.5
Hello,I saw that some system application fails the codesign verification on OSX 10.11.5.For example:Finder: codesign -v /System/Library/CoreServices/Finder.app /System/Library/CoreServices/Finder.app: a sealed resource is missing or invalidQuickLookUIHelper: codesign -v /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/Resources/QuickLookUIHelper.app//System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/Resources/QuickLookUIHelper.app/: a sealed resource is missing or invalidquicklookd: codesign -v /System/Library/Frameworks/QuickLook.framework/Versions/A/Resources/quicklookd.app/System/Library/Frameworks/QuickLook.framework/Versions/A/Resources/quicklookd.app: a sealed resource is missing or invalidWhy the codesign failes for this application and posiblly others?Thanks,Tudor
0
0
431
Jun ’16
Reply to Xcode 8 Beta error launching simulator
Thanks for the tip, that command shows that no extraneous FinderInfo is associated with the object code. The only file in the framework directory that does have FInderInfo is .DS_Store:-rw-r--r--@ 1 gds wheel 6148 Jun 15 15:37 .DS_Store com.apple.FinderInfo 32Could that be what’s tripping codesign? Seems odd...Contrary to the original poster, my project is entirely Objective-C for OS X. Other frameworks in the same project are being codesigned fine.
Jun ’16
How can I fix this code signing issue? Error from non-existent folder
Hi,I have an code signing error that I cannot seem to fix. Our app is a game built in Unity.I am following the Unity docs (link below) to prepare the app for submission.http://docs.unity3d.com/Manual/HOWTO-PortToAppleMacStore.htmlI don’t encounter any errors on building, but after uploading with Application Loader (v. 3.5), I get the following error by email from Apple. (Portions have been redacted.):Dear developer,We have discovered one or more issues with your recent delivery for “GALAK-Z”. To process your delivery, the following issues must be corrected:Invalid Signature - The main app bundle Galak-Z at path Galak-Z.app has following signing error(s): code object is not signed at all In subcomponent: /Volumes/data01/app_data/dstr/mz_5855914490978851559dir/mz_637725543040462146dir/com.17-bit.galak-z.pkg/Payload/Galak-Z.app/Contents/Frameworks/Icon . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS
1
0
382
Jun ’16
Reply to New Individuals Membership
Yes.Before you can access 'Website Push IDs' via the Member Center, you need to have a paid Individual Developer Account.A 'Team' in terms of Xcode is currently a default for auto codesigning is why it's being pushed as a (top level) requirement. Push notifications are one of the things devs can utilize once enrolled, so you would need a paid Individual Developer Account in any case.See 'Supported Capabilities' here and be sure to read the notes for the table:https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/SupportedCapabilities/SupportedCapabilities.html#//apple_ref/doc/uid/TP40012582-CH38-SW1
Jun ’16
Reply to GateKeeper rejects my app in 10.11.4, which was working fine until 10.11.3
Thanks for your reply.It's written in Delphi. libcgunwind.1.0.dylib is reuired for the 'standard' unwinding of C exceptions.I tried moving this dylib to the Contents/Frameworks folder. This doesn't solve the obsolete resource envelope problem when trying to codesign the bundle. codesign -dvvv --deep /Users/Giel/Desktop/MyApp.app gives the same result (it reports a different dylib path of course).
Topic: Privacy & Security SubTopic: General Tags:
Jun ’16
Codesign Error
I developed an app and am trying to run it on my iPhone, but when I try to run the app, it says something like, Couldn't codesign, and then it has a directory that doesn't exist on my computer. Please help if you can. 😟
0
0
209
Jun ’16
Reply to Build ios app for device on sierra
Does anyone have a solution or workaround to this problem?I have the same issue - it works only in the simulator. Consistently fails at the codesign step. Tried just about all the suggestions - nothing has worked so far. error: A cryptographic verification failure has occurred.Or do we have to keep running only in the Simulator (rather than on the device) until a new Beta is available?
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’16
How to codesign command line application on 10.11.5
Signed on 10.11.5 command-line application doesn't pass the verification just after signing - spctl gives me an obsolete resource envelope error. So it doesn't run.I sign with the command:codesign -fs Developer ID Application: MyCompany path/to/cmd_appOn 10.11.1 and 10.10 (only we have) - GateKeeper allows to start it and application works properly.Are any new parameters or rules to codesign command line applications for running on 10.11.5?
0
0
1.3k
Jun ’16
XCode 8, Beta 1
Hi all,I am trying to run a Mac app that I developed in XCode 8, Beta 1 in MacOS Sierra. When I try to, I get the error: command /usr/bin/codesign failed with exit code 1I've tried resetting my Mac Developer Certificate and Cleaning the Build, but still no go.What can I do to fix this problem, other than reporting it to Apple.Thanks,Dan Uff
4
0
841
Jun ’16