Search results for

codesign

3,113 results found

Post

Replies

Boosts

Views

Activity

Reply to kext code signature is invalid
We are seeing the same issue with our UAD-2 system driver. I filed a bug about it, radar: 24270565.I looked into it, and the problem appears to be that we are code signing everything on our build machine which is running OS X 10.8. Ideally we’d be running a later OS, but suffice it to say there are reasons we can’t do that right now. Codesigning on 10.8 results in a “v1 resource envelope”, which is technically obsolete and results in codesign --verify -vvvv <path to kext>” reporting it as such. However, the kext has always actually loaded fine on all systems prior to this 10.11.4 beta, and kextutil -nt” would not report any issues. But on the 10.11.4 beta, kextutil -nt” now reports that the code signature is invalid, and won’t load the kext. I manually re-signed the kext on my 10.9.5 system, and now the kext loads fine on the 10.11.4 system (code signing on 10.9.5 results in the v2 resource envelope getting generated in the signature).The v1 resource envelope was an issue for apps dist
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’16
Reply to Can't export a Developer ID Signed App Suddenly
I can't seem to to resolve this.I'm guessing the latest OS update messed something up (to 10.11.3).Here's some logs2016-02-04 01:05:05 +0000 /var/folders/hl/msj8911s7wzg_z259xv0mr_80000gn/T/XcodeDistPipeline.GIx/Root/Applications/MYAPPNAME.app/Contents/Frameworks/SVGKit.framework/Versions/A/Frameworks/libswiftAppKit.dylib: timestamps differ by 187 seconds - check your system clock2016-02-04 01:05:05 +0000 /usr/bin/codesign exited with 12016-02-04 01:05:05 +0000 [MT] Proceeding to distribution step IDEDistributionSummaryStepViewController, context: <IDEDistributionContext: 0x7fa0ea55ffb0; archive(resolved)='<IDEArchive: 0x7fa0eb22c640>', distributionTask(resolved)='2', distributionMethod(resolved)='<IDEDistributionMethodDirectDistribution: 0x7fa0ea5a2940>', teamID(resolved)='team id here'> Chain (5, self inclusive): <IDEDistributionContext: 0x7fa0ea55ffb0; archive = '(null)', distributionMethod='(null)', teamID='(null)'> <IDEDistributionContext: 0x7fa0e81c64c0; archive = '(n
Feb ’16
No codesigning certificates found
Hello all, Hoping someone has come across this before? I unistalled xcode a few weeks ago, not sure if these issues are related?i have an app I would like to test on my Apple TV. I've just got the free dev account ATM. When I open iOS App Signer to generate the ipa file, I get the above error - No codesigning certificates found, you won't be able to successfully sign anything.There are no options in my Signing Certificate field. This all worked fine a few weeks ago when I loaded the app onto y iPad.Anyone have any ideas please?Thanks
9
0
29k
Feb ’16
The path does not contain IPA file
I'm creating a project using cordova CLI. The project is created successfully. The build also installed successfully on an iPhone. But when I try to upload the archive it throws errors: -1. An error occurred during upload. Codesign failed2. Error Domain=IDEFoundationErrorDomain Code=1 Codesign failed UserInfo={NSLocalizedDescription=Codesign failed}.3. Unable to validate your applicaiton. The path /var/folders/gk//*some_key*/T/XcodeDistPipeline.a6b/Packages/app_name,ipa does not contain a file.Note: - 1. My bitcode enabled is no.2. Certificate and provisional profile is valid and of distribution.Anyone please let me know how to fix this issue and what I'm doing wrong.
0
0
648
Feb ’16
OS X 10.11 Network Extension Invalid Code Signing Entitlements
Hi, Apple.I created Mac distribution profiles for OS X Container App and OS X Packet Tunnel Provider.And here is my projects' settings:Xcode - Building Settings - Code Signing - Code Signing Identity - Release - 3rd Party Mac Developer Application: xxxxxx (T5N*****)Xcode - Building Settings - Code Signing - Provisioning Profile - Release - Generated Distribution Profiles (Container app and OS X Packet Tunnel Provider) from Apple Developer CenterAnd when I was submiting it to iTunes Connect, it told me 'Invalid Code Signing Entitlement, key 'com.apple.developer.networking.HotspotHelper' is not supported on MAC OS X'. But my app doesn't need 'com.apple.developer.networking.HotspotHelper' entitlement, it just generated by Apple Developer Profile Distrubtion system. I can't submit my app to iTunes Connect.Please tell me how to resolve this problem.> codesign -d --entitlements :- xxx.app Executable=/Users/USER/Library/Developer/Xcode/DerivedData/xxxVPN-ecyoxdpkmfgtadhgpkyzjsgjiuvk/Build/Products/Debug/
2
0
1k
Feb ’16
xcbuild in Xcode Run-Script fails although terminal script works
Hi,I have a problem which I'm trying to solve in the last few weeks with no luck.I have a workspace contains two projects:1. A static library which creates a fat framework2. My main app which includes this framework.Until today I always went to the static library project and built it using aggregated target which builds iOS and simulator and combines them with lipo.This works fine. I then take the .framework and import it into my app with no issue.Lately I wanted to save the need to build the framework from its own project so I added a Run Script to my app's target which runs the same aggregation but from my app project and not the framework project, so each time I build my app I will get the latest framework build.This one however is not working and I'm getting build errors, especially related to entitlements missing (CodeSign error: entitlements are required for product type 'Bundle' in SDK 'Simulator - iOS 9.2'. Your Xcode installation may be damaged or [BEROR]CodeSign error: entitlements
0
0
1.1k
Mar ’16
How to verify signature of a package
In order to verify the signature of an application on disk, we can use SecStaticCodeCheckValidityWithErrors, which works as expected.However, if this is used on a signed package, the following error occurs The operation couldn’t be completed. (OSStatus error -67062.)Error 67062 also represents that an application is not signedIt appears that SecStaticCodeCheckValidityWithErrors only works with binary code or application bundles. To confirm this, calling codesign also fails to verify the signature of a package: codesign -dvvv myPackage.pkg myPackage.pkg: code object is not signed at allHow can we programmatically verify the signature of a package (pkg), without resorting to calling an external process such as pkgutil?
3
0
3.8k
Mar ’16
Difference between ios en .app distribution (Enterprise)
Greetings reader,I'm trying to grasp the difference for enterprise usage in mac or ios.We build custom enterprise apps for differenent customers, who will incluse us into their apple enterprise program as an admin. We used to did this for iOS, now we would like OS X as well.Do we still have to use their enterprise program to get a developer id certificate to codesign the .app? Or should we be able to sign that on our own?Thanks in advance
0
0
456
Mar ’16
Can I Clear all Developer Certificates
Over the years, I've built up quite a few developer certificates. Many have expired, some are marked as invalid, and others are duplicates created when trying to resolve specific codesign and productsign issues.I'm in Spring cleaning mode and I'd like to clear all of my existing certificates and start with a fresh set.Is this possible - how?Not Recommended - why?Tim
3
0
8k
Mar ’16
How to codesign against the executable binary by 'Go' language
Hello,I'm stucked at codesigning on a binary that is built with 'Go' language for Mac app.The 'Go' binary works as far as 'not signed'. But 'signed' binary does not work.Reference: https://github.com/atom/electron/blob/master/docs/tutorial/mac-app-store-submission-guide.mdBased on the code above, I used the following bash script (excerption) for codesigning:codesign --deep -fs '<my app sign title>' --entitlements child.plist '<app path>/Contents/Frameworks/Electron Framework.framework/Libraries/libnode.dylib' codesign --deep -fs '<my app sign title>' --entitlements child.plist '<app path>/Contents/Frameworks/Electron Framework.framework/Electron Framework' codesign --deep -fs '<my app sign title>' --entitlements child.plist '<app path>/Contents/Frameworks/Electron Framework.framework/' EnnoMac-darwin-x64/EnnoMac.app/Contents/Frameworks/Electron Framework.framework/: replacing existing signature codesign --deep -fs '<my app sign title&g
0
0
1.7k
Mar ’16
Reply to how to sign my kext.
I solved create Developer ID problem …Cool.But it build fails with kext-enable Developer ID.That seems pretty self explanatory: your system clock is 808 seconds off (almost 13 minutes). I recommend that you enable System Preferences > Date & Time > Date & Date > “Set date and time automatically”.Note Developer ID requires that the code signature include an accurate timestamp so that Developer ID certificates can be revoked effectively. Apple runs such a service (speaking the protocol described in RFC 3161) as timestamp.apple.com, and codesign talks to that service when signing using a Developer ID. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: App & System Services SubTopic: Core OS Tags:
Mar ’16
Invalid Signature Application Loader
Every time i send the app via Application Loader I receive an email saying that i haven't signed my app.I am confused as three months ago i did the same process as i am doing now and everything went ok.The process is the following:1. Sign the app with the Mac Developer Application cert2. Sign the entitlements3. Productbuild with Mac Developer Installer certI have to point out that when signing the entitlements i have to use sudo, otherwise it wont get signed and the Application Loader tells me.I use the following command to revise that everything is correct:codesign -dvvv --entitlements :-codesign -vThanks in advance
1
0
316
Mar ’16