“codesign”

I am building an IOS app for another company.I was using xcode 7 and was able to use xcodebuild to build an unsigned archive which I was able to give to the customer who would then use it to generate their app signed with their own id.It seems that with xcode 9 I now need to sign the archive. I think I could still do this with wild card developer id but the problem is that the app has group entitlements which are not allowed in wildcard ids.I do not want to have to have customers provide me with their codesigning certificates and provisioning files.This is the command line I use to use as part of a script run by Jenkins:xcodebuild archive -project <my_project> -scheme <my_sheme> -configuration Release -archivePath <my_archive_path> OTHER_CODE_SIGN_FLAGS='--keychain /Users/me/Library/Keychains/Buildsystem' CODE_SIGN_ENTITLEMENTS=/Users/me/entitlements.plist CODE_SIGN_IDENTITY= CODE_SIGNING_REQUIRED=NO HEADERMAP_INCLUDES_PROJECT_HEADERS=NO USE_HEADERMAP=NOThe provisioning file I was u

Our automatic signing system runs in an isolated network having tightly restricted connectivity, just to timestamping and some other necessary services. Timestamping occasionally fails when the IP addresses change. Configuring the IP address range for this in our firewall could increase the robustness of our internal code signing service.

I'm trying to run the sample code provided by Apple. I'm getting:/Users/me/Library/Developer/Xcode/DerivedData/ARKitImageRecognition-dbzdmsowoqmsaqejorbxkompvdfl/Build/Products/Debug-iphoneos/ARKitImageRecognition.app/Frameworks/libswiftARKit.dylib: unknown error -1=ffffffffffffffff error: Task failed with exit 1 signal 0 { /usr/bin/codesign '--force' '--sign' '02832D01E3EA1AF5F65ED0EB4934262B31E2FDDB' '--verbose' '/Users/me/Library/Developer/Xcode/DerivedData/ARKitImageRecognition-dbzdmsowoqmsaqejorbxkompvdfl/Build/Products/Debug-iphoneos/ARKitImageRecognition.app/Frameworks/libswiftARKit.dylib'I thought it might be DerivedData, but I've dumped that. Tried restarting. This error persists. Help?

Hi guys!I have an issue with review process in Mac App StoreApp was developed using Electron.I have done everything according to their instructions.I got .app and .pkg files.This package could not be loaded though Application Loader with errorERROR ITMS-90287: Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.developer.team-identifier' in 'xxxxxx/Payload/xxxxxxxx.app/Contents/MacOS/Xxxxxxx'.If I resign App with next scriptsign.sh#!/bin/bash APP=XXXXXXXXX APP_PATH=install/mas/Xxxxxxxxx.app RESULT_PATH=AppStore/$APP.pkg APP_KEY=3rd Party Mac Developer Application: XXXXXXXXXX (XXXXXXXXXXXXX) INSTALLER_KEY=3rd Party Mac Developer Installer: XXXXXXXXX (XXXXXXXXXXX) CHILD_PLIST=plists/child.plist PARENT_PLIST=plists/parent.plist LOGINHELPER_PLIST=plists/loginhelper.plist FRAMEWORKS_PATH=$APP_PATH/Contents/Frameworks codesign

Hi,I'm developing macOS Apps using Adobe Air. This used t owork quite well! Now I've finished a new macOS App and I'm trying to use my old script (which always worked before) but it seems Apple changed something.When I use this script in Terminal:cd /Users/essig/Desktopcp MacProcess/Info.plist Europa meistern.app/Contents/Info.plistcp MacProcess/Icon.icns Europa meistern.app/Contents/Resources/Icon.icnschmod -R 777 Europa meistern.appcodesign -f -v -s 3rd Party Mac Developer Application: Jan Essig Europa meistern.app/Contents/Frameworks/Adobe AIR.framework/Versions/Current/Adobe AIR_64 Helpercodesign -f -v -s 3rd Party Mac Developer Application: Jan Essig Europa meistern.app/Contents/Frameworks/Adobe AIR.framework/Versions/Current/Adobe AIR_64codesign -f -v -s 3rd Party Mac Developer Application: Jan Essig Europa meistern.app/Contents/Frameworks/Adobe AIR.framework/Versions/Current/Adobe AIRcodesign -f -v -s 3rd Party Mac Developer Application: Jan Essig Europa meistern.app/Contents/MacOS/Europa meisternc

I switched a project to the New Build System to see what it was like. The result was not good. My app is created, but fails upon launch due to a codesign error. What is strange is that codesign says all is OK. Also, switching back to the default build system resolves the issue.$ codesign -dv old-build-system/GeoTag.app (copied the build folder to the desktop to compare with the new build system code) Executable=/Users/marc/Desktop/Build/Products/Debug/GeoTag.app/Contents/MacOS/GeoTag Identifier=org.snafu.GeoTag Format=app bundle with Mach-O thin (x86_64) CodeDirectory v=20200 size=4752 flags=0x0(none) hashes=141+5 location=embedded Signature size=4685 Signed Time=Feb 23, 2018 at 4:48:01 PM Info.plist entries=28 TeamIdentifier=A3UXBEBE8Z Sealed Resources version=2 rules=13 files=242 Internal requirements count=1 size=176$ codesign -dv new-build-system/GeoTag.app Executable=/Users/marc/Library/Developer/Xcode/DerivedData/GeoTag-aqjdodmrxrygnggelbxhetiiwrcm/Build/Products/Debu

Hello - I have a membership as an Apple Developer - I have been deploying and testing apps for some time and suddenly I am getting a code signing error. I am not sure what has changed? I have tried numerous solution/suggestion on the forum with no luck. -I have deleted the KeyChain access certificates and re-created via xcode. I have looked at the immediate and root certificates but not sure which ones I need - tried a number of them. I did register an app in the iTunesConnect to begin the process of submiting for approval - but that shouldn't impact my development workflow when deploying to phone? Any guidance is much appreciated.Warning: unable to build chain to self-signed root for signer iPhone Developer: Name (xxxxxxxxxxxxx)/Users/Name/Library/Developer/Xcode/DerivedData/Unity-iPhone-ctglawntjuiiaacqkcyropceltlb/Build/Products/ReleaseForRunning-iphoneos/AppTestName.app: unknown error -1=ffffffffffffffffCommand /usr/bin/codesign failed with exit code 1Thank you!

I have an app that adds some items to the keychain. I've noticed recently that when upgrading the app, the system pops up the allow access to this keychain item dialog when it attempts to read a keychain item that was added by the previous version. This app is codesigned and passes all codesign diagnostics. Did something change recently that causes this permission request to pop up even though the both versions of the app are signed with the exact same certificate.I will state that the app is not signed with a Developer ID Application certificate but with a valid code signing certificate from a non-Apple CA. Is there some new requirement that a Developer ID Application certificate must be used in order to not see this prompt when an app is upgraded?I dumped the keychain using security dump-keychain -a before and after upgrade and the only difference between the item is that the partition_id entry contains an additional cdhash for the new app. From what I understand cdhash will change when th