“codesign”

Running on Sierra I found that Keychain Access is no longer updated with a new keychain created with security create-keychain.So what happens is:1. security delete-keychain <keychain> ; this actually deletes the keychain and removes from Keychain Access2. security create-keychain <keychain> ; this creates the keychain however it does not populate to Keychain Access unless it is the login.keychain[-db] - which it is not3. security find-identity <keychain> -p codesigning -v ; fails even after adding .p12 and .cer / .pem files4. unlocking the keychain does not help, setting default-keychain does not help either as those do not populate the created keychain into Keychain Access5. opening Keychain Access and selecting File / Add Keychain... is the only thing what helps and makes security find-identity <keychain> -p codesigning -v successfulThe problem is that I create the keychain with about 40 keys and certs in a batch job on a build machine so adding the signing identite

I have a project that uses Swift and Objective, no Cocoapods.Shortly after uploading my IPA through Application Loader I received this email from Apple:Dear developer,We have discovered one or more issues with your recent delivery for EdgevisTest. To process your delivery, the following issues must be corrected:Invalid Swift Support - The file libswiftAVFoundation.dylib doesn’t have the correct code signature. Make sure you’re using the correct signature, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Don’t just modify the code signature of libswiftAVFoundation.dylib.Once these issues have been corrected, you can then redeliver the corrected binary.Regards,The App Store teamI should point out that I have used a script to resign the IPA for a customer. Any ideas what I can do to sort this?Attached below is the script I have used.# !/bin/bash SOURCEIPA=$1 DEVELOPER=$2 MOBILEPROV=$3 TARGET=$4 BUNDLE=$5 unzip -qo $SOURCEIPA -d extracted APPLICATION=$(ls extracted/Payload/) #Remo

I code signed a dylib, and spctl says rejected (the code is valid but does not seem to be an app). Well, I didn't say it was an app, I just want to be sure that it is properly codesigned. I could swear this used to work.

I'm trying to get a DNS Proxy working in iOS 11.0 beta 2. I have the entitlements, and I have enabled the DNS proxy through the manager but it isn't calling startProxy in my Proxy Provider. I'm able to loadFromPreferences() so I think the entitlements are correct and isEnabled shows true when I move the app to the background and back to the foreground. Any help would be great.In my main app:func applicationDidBecomeActive(_ application: UIApplication) { let manager = NEDNSProxyManager.shared() if manager.isEnabled == true { NSLog(enabled) } else { manager.localizedDescription = DNS Proxy manager.loadFromPreferences { error in if (error != nil) { NSLog(Load error: (String(describing: error?.localizedDescription))); } else { NSLog(loaded preferences); let dict = [foo: bar] let proto = NEDNSProxyProviderProtocol() proto.providerConfiguration = dict proto.providerBundleIdentifier = com.bangj.DNS.DNS-Proxy manager.providerProtocol = proto manager.isEnabled = true } } } }My Proxy Provider:class DNSProxyProvider: NE

so, the subject says it all.I literally include a 30x30 png in my bundle... which is a plugin... and the entire app will not compile.all I'm trying to do is store resources for the plugin, IN the plugin, and then retrieve them when I need them.this isn't a code thing, I can't even get through the first step: copying the images into the bundle causes this issue:.../Xcode/DerivedData/concrete-avagvvzvpkupkmeubvvuggphmrsf/Build/Products/Debug/CentralDogma.plugin: replacing existing signature.../Xcode/DerivedData/concrete-avagvvzvpkupkmeubvvuggphmrsf/Build/Products/Debug/CentralDogma.plugin: resource fork, Finder information, or similar detritus not allowedCommand /usr/bin/codesign failed with exit code 1been doing google searches for hours. I just need to know what I'm doing wrong.

Hello, From last few days I am facing one strange problem while archiving my app using developer id signed. I am getting an error when I try to export archive saying Error occured during export, code sign failed. I am also getting this log in the console signature too large to embed (size limitation of on-disk representation). I also noticed one strange thing, archive export works fine for project written in pure Objective C language and this problem exists for project written in pure swift and objective C + swift mixed language. I also checked provision profile and other certificates, everything is fine (No expired certificates). Can anyone please provide solution for this?Regards,Rohith Nayak

Hi,We are unable to codesign our Mac app using Developer Id Application certificate. This was workig fine till last week.If we set timestamp option to none everyting works fine. As we are distributing this app to public, can not use timestamp=none option.This error occurs only if app bundle has any framework or dylib. As we use swift in our application, swift dylibs will be emebeded with in the app.I am using Xcode 8.3.3 and Mac OS 10.12.4. I have also attached error logs here.Can anyone help me resolve this?Test-MBP$ codesign -s SIGNING_IDENTITY” —deep test123.app --force -o library test123.app: replacing existing signature test123.app: signature too large to embed (size limitation of on-disk representation) In subcomponent: test123.app/Contents/Frameworks/libswiftCore.dylib

I keep getting this error despite having installed new certificates. I have 3rd Party Mac Developer Application, AddTrust External CA Root, Apple Application Inegration Certification Authority, Developer ID Application, Apple Worldwide Developer Relations Certification Authority, Developer ID Application, Developer ID Certification Authority, Developer ID Installer and some others. Why does it give me this error?