“codesign”

I've configured a vpn (packet tunnel) on OSX, but I can't start it because of an entitlement problem(I already did it on iOS, but on OSX it's not running, although the entitlements suppose to work on both iOS and OSX)When I run the app, it's imediatly crashes with the error:... because its use of the com.apple.developer.networking.networkextension entitlement is not allowedaccording to this error, the containing app is not allowed to use the entitlements - but why??But if in the project settings, at the containing app, I remove the path to the entitlement file at Code Signing Entitlements, the app won't crash, but not start the VPN.To check what's the problem, I ran at the terminal codesign -d --entitlements :- CatoClient.appand codesign -d --entitlements :- CatoClientExtension.appexIn both of them I can see<array><string>packet-tunnel-provider</string><string>app-proxy-provider</string><string>content-filter-provider</string></array>Any Help w

Hello,I am using key-value storage to save and synchronize data in iCloud. While this works well for all iOS Devices, Apple TV does not synchronize with the iOS devices.I checked the entitlements file with codesign -d --entitlements :- myApp.app, it is the exact same on the iOS and tvOS app.However, apparently tvOS uses a different container than iOS. Did anyone experience this issue as well? Any help is greatly appreciated! Also, does anybody know how can check the Key-Value-Storage container url at runtime?

I have an app that customers download from the web. This downloaded app was working fine until 10.11.3, my users started seeing an error started with 10.11.4. I havent changed the signing process (or the bundle) between 10.11.3 and 10.11.4. The error that users see is : MyApp can't be opened because the identity of the developer cant be confimed.After a bit of reading about this on Apple developer forums a bit more here are the results:codesign results are successfulcodesign --verbose=4 --deep --strict MyApp.app/InstallForMacOSX.app/: valid on diskInstallForMacOSX.app/: satisfies its Designated RequirementMore details on codesign:codesign -dvvv MyApp.appFormat=bundle with genericCodeDirectory v=20200 size=240 flags=0x0(none) hashes=1+4 location=embeddedSignature size=8926Authority=Apple Root CATimestamp=Apr 13, 2016, 1:00:14 PMInfo.plist entries=2Sealed Resources version=2 rules=12 files=1Internal requirements count=2 size=224spctl returns an error:This is the same error described in other threads.spctl --raw

I realize that this forum is not the place to report bugs. I've already reported this bug via the Apple Bug Reporter. After they asked for additional data (which I immediately supplied) I have not heard anything from Apple in 7 weeks (despite poking them.) I'm hoping someone here has seen this and might be able to suggest a workaround. Without a solution or workaround, I cannot submit my app to the Apple Store.The problem is that when trying to verify or submit the application to the store from the XCode Archive Organizer, XCode 7.3 crashes.The archive organizer goes through a bunch of Processing symbols.... phases followed by a bunch of Codesigning .... steps and then crashes while the display shows Codesigning AppName.app. It's not clear if it is crashing during the Codesigning of AppName.app or if the crash happens immediately after that.If it matters, the app in question is built with GWT, mGWT, and Phonegap/Cordova.Running the application works fine on iOS simulators as well as

I have an existing app with the App ID. I am trying to turn on push notification for it. However, it says An App ID with Identifier is not available.. I tried deleting all certificates and all profiles and starting all over. But I could not get it to work!If I manually setting Code Sign Identity it says No codesigning identities (i.e. certificate and private key pairs) that match your provision profile specified in your built setting were found. If I let it auto-fix it goes back to saying the App ID is not available again.

Hey all,I have an unusual Kext signing issue,it might actually be very simple, but i'm not sure.I create applications and installers for distribution outside of the App store,including a Kext driver for PCI-E device that my company makes.So a while back i signed up for all the appropriate provisioning profiles etc.Including contacting apple to get certified as a proper kernel developer so wecan get our Kext Signed appropriately.Everything was working fine.I recently noticed that Xcode was indicating that the status of my signing identitieswas Revoked I was a bit concerned about this and proceeded to refresh them from withinXcode. Now Xcode lists the following Signing identities: ( Mac only)Mac DevelopmentMac App DistributionMac Installer DistributionDeveloper ID applicationDeveloper ID InstallerAnd a single Provisioning Profile:Mac Team Provisioning Profile: *Building and signing Apps and installers all seems to be fine, but it appears that when I sign my kext driver it is no good?I am signing the Kext projec

Hello,I have codesigned quite a lot of apps in the past, but didn't do it for a while.I codesign via the termial (no Xcode): codesign -s MyCertificateName --deep -force myApp.appNow I get the error: invalid argument rceI don't see, where I used an argument rce and what could be the issue here.Any ideas what is going wrong here?ThanksTiemo

Signing a .app that wraps a shell script using OS X 10.11 fails to verify on 10.10 or below. I can sign on 10.10 and 10.9 and it verifies on 10.9, 10.10 and 10.11.I've put two example apps and a script on [github][1] to show this. The two HelloWorld.app's vary only in the binary in Contents/MacOS/HelloWorld. One is a shell script, the other is compiled objective-c.Signing works and verifies on 10.11 for both versions:Shell Script version: codesign -s ${signing_identity} -v shell-script/HelloWorld.app signed bundle with generic [liamsharp.helloworld] codesign -vv shell-script/HelloWorld.app shell-script/HelloWorld.app: valid on disk shell-script/HelloWorld.app: satisfies its Designated RequirementObjective-C version: codesign -s ${signing_identity} -v objective-c/HelloWorld.app signed bundle with Mach-O thin (x86_64) [liamsharp.helloworld] codesign -vv objective-c/HelloWorld.app objective-c/HelloWorld.app: valid on disk objective-c/HelloWorld.app: satisfies its Designated Re

I'm trying to update an app. It's acceptted by the Application Loader but soon afterwards I get an email that says:Invalid Signature - The binary with bundle identifier 'com.velocedge.hypothesistesting' at path [Hypothesis.app] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate.I've revoked my distribution certificates, recreated them and the distribution mobileprofile, yet I keep getting the message. I used codesign to see what's inside the app and got the following. From what I can tell, they look like distribution to me but I don't really know what I'm looking at.$ codesign -dvvv Hypothesis.app/Executable=/Users/macuser/Desktop/certificates/Velocedge/Payload/Hypothesis.app/HypothesisIdentifier=com.velocedge.hypothesistestingFormat=bundle with Mach-O universal (armv7 arm64)CodeDirectory v=20001 size=92276 flags=0x0(none) hashes=4605+5 location=embeddedHash type=sha1 size=20CDHash=

I code sign my mac app with Mac Developer and now I can not run my UT.It fails on build with the message:AAA.app: bundle format unrecognized, invalid, or unsuitable In subcomponent: AAATests.xctestI make sure everything is codesign with the same certificate.Any Idea?

Hey,I just got my Developer ID. I've developed a dashboard widget, but I have no idea how to sign it. It's a .wdgt package, that contains the plist.info in its root. How do I get the certificate? Do I need to sign it with Xcode or something? Or, do I use codesign from the command prompt - and how do I do that?Cheers,Taylor