Search results for

“codesign”

3,221 results found

Post

Replies

Boosts

Views

Activity

Reply to "No identity found" error when codesigning app
In Keychain Access, I selected my Developer ID certificates and then had Keychain Access evaluate them. The Developer Application certificate is good for codesigning. The Developer Installer certificate, though, is listed as Invalid Extended Key Usage. The 3rd Party Mac Developer Application certificate is listed as Success and Good. I believe this certificate is for another app specifically, though, one i'd tried to get into the App Store before, but it was turned down because it used QuickTime, a legacy app. Tried creating a wild card certificate, but it won't let me install it. It says Only Development Provisioning Profiles can be installed in System Preferences. Production Provisioning Profiles are imported within Xcode. No idea what that means. Wish i could just hire someone to do this for me. It's ridiculous.
Topic: Code Signing SubTopic: General Tags:
Aug ’17
Mac App store Code Signing EXC_CRASH (Code Signature Invalid)
Hello -We have been trying for the past 2 days to get our Mac App submitted passed through the Mac App review process. We have updated our signing certificates and even created new provisioning profiles for signing and using the XCODE - Organizer to validate and upload to the Mac App store. We confirmed the bundle receipt etc.However the Mac App store review board keeps on telling us our app is crashing on launch time with the following under 10.12.6 during the review process:Exception Type: EXC_CRASH (Code Signature Invalid)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYTermination Reason: Namespace CODESIGNING, Code 0x1Termination Details: CODESIGNING, When validating /Applications/PDF2Office for iWork 2017.app/Contents/MacOS/PDF2Office for iWork 2017: Code has restricted entitlements, but the validation of its code signature failed.Unsatisfied Entitlements:We are using 10.11.6 and XCODE 7.3.1 but we just dont get it. The App review were able to tes
Topic: Code Signing SubTopic: General Tags:
12
0
17k
Aug ’17
URLForUbiquityContainerIdentifier returning nil for valid, containerId, entitlements
I can't for the life of me get URLForUbiquityContainerIdentifier to work for my iCloud container on iOS. I have:Added the iCloud container to the app & provisioning profile on developer portal.Set the iCloud entitlements including containers in Xcode.Verified the team ID and entitlements in the signed app bundle:turin:pkdiagram patrick$ codesign -d --ent :- build/ios/Debug-iphoneos/Family Diagram.app Executable=/Users/patrick/dev/pkdiagram/build/ios/Debug-iphoneos/Family Diagram.app/Family Diagram <?xml version=1.0 encoding=UTF-8?> <!DOCTYPE plist PUBLIC -//Apple//DTD PLIST 1.0//EN http://www.apple.com/DTDs/PropertyList-1.0.dtd> <plist version=1.0> <dict> <key>application-identifier</key> <string>8KJB799CU7.com.vedanamedia.familydiagram</string> <key>aps-environment</key> <string>development</string> <key>com.apple.developer.icloud-container-identifiers</key> <array> <string>iCloud.com.vedanamedia.fami
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
1.8k
Aug ’17
Reply to Developer ID code sign Error
This isn’t really my field but your problem looks similar to one that’s been reported to DTS a few times. According to the colleague I talked to (DTS’s expert on code signing issues) there’s been recent changes to how Apple’s timestamp server works and that seems to be triggering the issue. The folks responsible know about this problem but, for the moment, you might be able to work around it by adding --signature-size=12000 to your codesign command. Please try this out and let us know how you get along.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: General Tags:
Aug ’17
Reply to Mac App store Code Signing EXC_CRASH (Code Signature Invalid)
Just to let everyone know, we generated updated distribution profiles and built under 10.12.6 and submitted and it worked I guess. I have no clue why, but seems like there must have been some kind of bug either with XCODE and codesigning under 10.11.x or something changed in Apple's back end which we have no idea about that must have affected code signing recently.
Topic: Code Signing SubTopic: General Tags:
Aug ’17
PacketTunnelProvider crashing immediately when profiling memory leaks?
I'm trying to profile memory leaks in my PacketTunnelProvider, however when I try to do this the profiler immidiately crashes.My process is as follows:In XCode, go to Product->ProfileWait for Instruments to launchSelect Memory Leaks from the instruments launch screen.Launch my application on my phone and verify that the PacketTunnelProvider has been initialized.In Instruments, select my Provider's process.Click the record buttonWhen I do this, the Provider's process immidiately crashes.Below is the crash important pieces of the crash log:Incident Identifier: 52385F44-7415-46BB-9B2D-81D7E95A8DAF CrashReporter Key: 36ba17b72c93e0740152f3fd33ca4799c2227c51 Hardware Model: iPhone8,1 Process: NAFTVPNProvider [1654] Path: /private/var/containers/Bundle/Application/E1705D53-980B-4010-91FD-EB480071BE6B/NAFT.app/PlugIns/NAFTVPNProvider.appex/NAFTVPNProvider Identifier: com.NAFT.vpn.provider Version: 1504224015 (2017.8.31) Code Type: ARM-64 (Native) Role: Unspecified Parent Process: launchd [1] Coalition: com.NAFT.v
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
850
Sep ’17
Reply to xcode/cordova signing errors
I have Sierra OS and having a issue with cordova command line build - trying to create ipa from command line for automationThe build and archive works perfectly fine when done from XCode IDE, but when using CLI i get the error pasted below.Command: cordova build ios --device --buildConfigI have used correct provisioning profile and team etc in build.jsonWhat is this .app: unknown error -1=ffffffffffffffff how to solve it?/usr/bin/codesign --force --sign 12C94CXXXXXXXXXXXXXXX16E9AEBF6AB06ADD --entitlements /Users/XXXX/Library/Developer/Xcode/DerivedData/XXXX_XXXX-bznjdwrmpxxmzudbdvcjspewllmt/Build/Intermediates/ArchiveIntermediates/XXXX XXXX/IntermediateBuildFilesPath/XXXX XXXX.build/Release-iphoneos/XXXX XXXX.build/XXXX XXXX.app.xcent --timestamp=none /Users/XXXX/Library/Developer/Xcode/DerivedData/XXXX_XXXX-bznjdwrmpxxmzudbdvcjspewllmt/Build/Intermediates/ArchiveIntermediates/XXXX XXXX/InstallationBuildProductsLocation/Applications/XXXX XXXX.app/Users/XXXX/Library/Developer/Xcode/DerivedData/XXXX_XX
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Sep ’17
Command builtin-swiftStdLibTool emitted errors but did not return a nonzero exit code to indicate failure
When trying to build application using commandXcodebuild -project Project.xcodeproj -scheme Trainer -configuration Release -xcconfig Config.xcconfig clean archive -archivePath build/ApplicationGetting below error /usr/bin/codesign '--force' '--sign' 'A8757475EA62AAF09FFC150F654421253EDF490E' '--verbose' '/Users/Library/Developer/Xcode/DerivedData/Trainer-esvcuzaerwfcyzdsyzzjcpjvcwui/Build/Intermediates/ArchiveIntermediates/Trainer/InstallationBuildProductsLocation/Applications/QA Member Connect.app/Frameworks/libswiftFoundation.dylib'2017-08-09 21:25:22.567056-0500 codesign[2529:23876] [security_exception] MacOS error: -67062/Users/ash/Library/Developer/Xcode/DerivedData/Trainer-esvcuzaerwfcyzdsyzzjcpjvcwui/Build/Intermediates/ArchiveIntermediates/Trainer/InstallationBuildProductsLocation/Applications/QA Member Connect.app/Frameworks/libswiftCoreLocation.dylib: code object is not signed at all2017-08-09 21:25:22.567234-0500 codesign[2531:23879] [security_exception] MacOS error: -670
Topic: Programming Languages SubTopic: Swift Tags:
0
0
728
Sep ’17
codesign xpc
We are having issues code signing correctly the XPC services that are deployed with our app.When checking in CLI I see the followingspctl --assess --verbose ./xxxxxx-xpc.xpc./xxxxxxx-xpc.xpc: rejected (the code is valid but does not seem to be an app)I really don't know where to take it from here. All targets are set to automatically manage sigining.There is very little on the web about examples to how to porperly codesign XPC services.We are using XCode 8.3.3The XPC services reside in Contents/XPCServicesCan anyone provide some guidance ?
Topic: Privacy & Security SubTopic: General Tags:
4
0
1.5k
Sep ’17
Reply to codesign xpc
ok so doing some further test what is happening when launching the app that is codesigned for the first time.The XPC service needs to access the main.app keychain Username and Password in order to then chat with web services. When the app is first installed there is an OS allert indicating that XPC is trying to access the Main.app keychain entry , [Always Allow] [ Deny] [Allow] . I would like to avoid this step so that the XPS service is allowed automatically and user does not need to provide input. if XPC is a target of the same app wouldd the system see it as part of it and not have to ask ?My initial thought is that the system is asking to allow the entry because the XPC services are not certified correctly but maybe there is more or something different to it ?Anyone ?
Topic: Privacy & Security SubTopic: General Tags:
Sep ’17
"Automatically manage signing" doesn't use the right AppID prefix
Hello everyone,I created and published an iOS application some years ago (2010) on the App Store.I didn't update it since, but I want to update it to be ARM64, so it runs on iOS 11.The project by itself was much too old (I don't remember with which version of Xcode I created it - probably Xcode 4) and upgrade to Xcode 8 doesn't work that much. So I decided to create a fresh new project with the exact same name and exact same product identifier (say it's com.mycompany.myapp), and re-added all sources of the old project.The project is configured to use Automatically manage signing, and work very well inside the simulator, and on my iPhone 6. So far, so good.But now, I try to release this update on the App Store, and when validating my stuff, it fails by saying :- On Xcode 8.3.3 : no matching provisioning profiles found for 'XXX'.- On Xcode 9.0 GM : Provisioning profile failed qualification — Profile doesn't match the entitlements file's value for the application-identifier entitlement.I tried with and without h
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
0
0
1.7k
Sep ’17
/usr/bin/codesign failed with exit code 1 cause:No such file or directory
CodeSign /Users/fanqianwen/Library/Developer/Xcode/DerivedData/iMOKO-duxwwacqnokyogbaoufeiplaswao/Build/Products/Debug-iphonesimulator/iMOKO.app cd /Users/fanqianwen/meituan/iMOKO/iMOKO export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin Signing Identity: - /usr/bin/codesign --force --sign - --timestamp=none /Users/fanqianwen/Library/Developer/Xcode/DerivedData/iMOKO-duxwwacqnokyogbaoufeiplaswao/Build/Products/Debug-iphonesimulator/iMOKO.app /Users/fanqianwen/Library/Developer/Xcode/DerivedData/iMOKO-duxwwacqnokyogbaoufeiplaswao/Build/Products/Debug-iphonesimulator/iMOKO.app: No such file or directory Command /usr/bin/codesign failed with exit code 1when linking period ,the error occur ?what should I do ?w
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
0
0
1.4k
Sep ’17
Reply to Mac App store Code Signing EXC_CRASH (Code Signature Invalid)
I can't comment on how to prevent a provisioning profile to break. But if you get your app rejected during App Store review due to a CODESIGNING crash (without having changed anything relevant), you could try the following if you let Xcode manage code signing automatically in your project:1) Delete all your provisioning profiles in your Apple developer account2) Rebuild and archive your app3) Before uploading it to the app store, you are shown the provisioning profile in use. There's a small link next to it. Click it and it shows you a cached version on your local drive in Finder. If the creation date of this one is old, move it (and all other cached provisionining profiles) away, e.g. to the Desktop folder.4) Cancel the upload to the app store.5) Rebuild and archive your app again. This time Xcode is forced to create a new provisioning profile and a new upload to the app store should now work.This fixed the problem for me, but I have no idea why the problems happen in the first place.== Matthias
Topic: Code Signing SubTopic: General Tags:
Sep ’17
Reply to Xcode 9 produces invalid Code Signature
I think I tracked down the issue. While manually checking the code signature of every framework contained in the bundle using codesign -vv, I discovered some frameworks returned an error with the following message: the sealed resource directory is invalid. Interestingly, only the frameworks built using Xcode 9 and Swift 4 are affected, older ones created with Xcode 8 and ObjC are fine. Also, the check doesn't produce an error on 10.12.Edit:It was because of the deployment target of the frameworks, but this also doesn't solve main issue.Edit 2:In fact, this solved the issue for the Developer ID-signed version, but the MAS-signed version is still broken.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Sep ’17
Signing an app and adjust its content afterwards (signature should remain unbroken)
Currently we are signing our application with the following way:codesign --force --verify --verbose --sign certificate's name application.app/Contents/MacOS/appBinaryWe are using Mac OS X 10.8 for signing since on newer systems this usage of codesign is not working anymore.When checking the signature of the application bundle withcodesign -vvvon OS X 10.9 or later it says: resource envelope is obsolete (version 1 signature). So obviously it is version 1 signed. But even if it appears to have a deprecated signature it does not cause any harm when running the app on OS X 10.9 (or later).Now we've also tested signing on OS X 10.9 by using:codesign --deep application.app -s certificate's nameWhen checking the signature it returns: valid on disk and satisfies its Designated Requirement. And it validated all files within the bundle. So obviously this is a valid version 2 signature.Now there is one reason we currently stick to the version 1 signing: When signing the application it inherits a certain number
Topic: Developer Tools & Services SubTopic: Developer Forums Tags:
1
0
4.5k
Sep ’17
Reply to "No identity found" error when codesigning app
In Keychain Access, I selected my Developer ID certificates and then had Keychain Access evaluate them. The Developer Application certificate is good for codesigning. The Developer Installer certificate, though, is listed as Invalid Extended Key Usage. The 3rd Party Mac Developer Application certificate is listed as Success and Good. I believe this certificate is for another app specifically, though, one i'd tried to get into the App Store before, but it was turned down because it used QuickTime, a legacy app. Tried creating a wild card certificate, but it won't let me install it. It says Only Development Provisioning Profiles can be installed in System Preferences. Production Provisioning Profiles are imported within Xcode. No idea what that means. Wish i could just hire someone to do this for me. It's ridiculous.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Aug ’17
Mac App store Code Signing EXC_CRASH (Code Signature Invalid)
Hello -We have been trying for the past 2 days to get our Mac App submitted passed through the Mac App review process. We have updated our signing certificates and even created new provisioning profiles for signing and using the XCODE - Organizer to validate and upload to the Mac App store. We confirmed the bundle receipt etc.However the Mac App store review board keeps on telling us our app is crashing on launch time with the following under 10.12.6 during the review process:Exception Type: EXC_CRASH (Code Signature Invalid)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYTermination Reason: Namespace CODESIGNING, Code 0x1Termination Details: CODESIGNING, When validating /Applications/PDF2Office for iWork 2017.app/Contents/MacOS/PDF2Office for iWork 2017: Code has restricted entitlements, but the validation of its code signature failed.Unsatisfied Entitlements:We are using 10.11.6 and XCODE 7.3.1 but we just dont get it. The App review were able to tes
Topic: Code Signing SubTopic: General Tags:
Replies
12
Boosts
0
Views
17k
Activity
Aug ’17
URLForUbiquityContainerIdentifier returning nil for valid, containerId, entitlements
I can't for the life of me get URLForUbiquityContainerIdentifier to work for my iCloud container on iOS. I have:Added the iCloud container to the app & provisioning profile on developer portal.Set the iCloud entitlements including containers in Xcode.Verified the team ID and entitlements in the signed app bundle:turin:pkdiagram patrick$ codesign -d --ent :- build/ios/Debug-iphoneos/Family Diagram.app Executable=/Users/patrick/dev/pkdiagram/build/ios/Debug-iphoneos/Family Diagram.app/Family Diagram <?xml version=1.0 encoding=UTF-8?> <!DOCTYPE plist PUBLIC -//Apple//DTD PLIST 1.0//EN http://www.apple.com/DTDs/PropertyList-1.0.dtd> <plist version=1.0> <dict> <key>application-identifier</key> <string>8KJB799CU7.com.vedanamedia.familydiagram</string> <key>aps-environment</key> <string>development</string> <key>com.apple.developer.icloud-container-identifiers</key> <array> <string>iCloud.com.vedanamedia.fami
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
1.8k
Activity
Aug ’17
Reply to Developer ID code sign Error
This isn’t really my field but your problem looks similar to one that’s been reported to DTS a few times. According to the colleague I talked to (DTS’s expert on code signing issues) there’s been recent changes to how Apple’s timestamp server works and that seems to be triggering the issue. The folks responsible know about this problem but, for the moment, you might be able to work around it by adding --signature-size=12000 to your codesign command. Please try this out and let us know how you get along.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Aug ’17
Reply to Mac App store Code Signing EXC_CRASH (Code Signature Invalid)
Just to let everyone know, we generated updated distribution profiles and built under 10.12.6 and submitted and it worked I guess. I have no clue why, but seems like there must have been some kind of bug either with XCODE and codesigning under 10.11.x or something changed in Apple's back end which we have no idea about that must have affected code signing recently.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Aug ’17
PacketTunnelProvider crashing immediately when profiling memory leaks?
I'm trying to profile memory leaks in my PacketTunnelProvider, however when I try to do this the profiler immidiately crashes.My process is as follows:In XCode, go to Product->ProfileWait for Instruments to launchSelect Memory Leaks from the instruments launch screen.Launch my application on my phone and verify that the PacketTunnelProvider has been initialized.In Instruments, select my Provider's process.Click the record buttonWhen I do this, the Provider's process immidiately crashes.Below is the crash important pieces of the crash log:Incident Identifier: 52385F44-7415-46BB-9B2D-81D7E95A8DAF CrashReporter Key: 36ba17b72c93e0740152f3fd33ca4799c2227c51 Hardware Model: iPhone8,1 Process: NAFTVPNProvider [1654] Path: /private/var/containers/Bundle/Application/E1705D53-980B-4010-91FD-EB480071BE6B/NAFT.app/PlugIns/NAFTVPNProvider.appex/NAFTVPNProvider Identifier: com.NAFT.vpn.provider Version: 1504224015 (2017.8.31) Code Type: ARM-64 (Native) Role: Unspecified Parent Process: launchd [1] Coalition: com.NAFT.v
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
2
Boosts
0
Views
850
Activity
Sep ’17
Reply to xcode/cordova signing errors
I have Sierra OS and having a issue with cordova command line build - trying to create ipa from command line for automationThe build and archive works perfectly fine when done from XCode IDE, but when using CLI i get the error pasted below.Command: cordova build ios --device --buildConfigI have used correct provisioning profile and team etc in build.jsonWhat is this .app: unknown error -1=ffffffffffffffff how to solve it?/usr/bin/codesign --force --sign 12C94CXXXXXXXXXXXXXXX16E9AEBF6AB06ADD --entitlements /Users/XXXX/Library/Developer/Xcode/DerivedData/XXXX_XXXX-bznjdwrmpxxmzudbdvcjspewllmt/Build/Intermediates/ArchiveIntermediates/XXXX XXXX/IntermediateBuildFilesPath/XXXX XXXX.build/Release-iphoneos/XXXX XXXX.build/XXXX XXXX.app.xcent --timestamp=none /Users/XXXX/Library/Developer/Xcode/DerivedData/XXXX_XXXX-bznjdwrmpxxmzudbdvcjspewllmt/Build/Intermediates/ArchiveIntermediates/XXXX XXXX/InstallationBuildProductsLocation/Applications/XXXX XXXX.app/Users/XXXX/Library/Developer/Xcode/DerivedData/XXXX_XX
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Sep ’17
Command builtin-swiftStdLibTool emitted errors but did not return a nonzero exit code to indicate failure
When trying to build application using commandXcodebuild -project Project.xcodeproj -scheme Trainer -configuration Release -xcconfig Config.xcconfig clean archive -archivePath build/ApplicationGetting below error /usr/bin/codesign '--force' '--sign' 'A8757475EA62AAF09FFC150F654421253EDF490E' '--verbose' '/Users/Library/Developer/Xcode/DerivedData/Trainer-esvcuzaerwfcyzdsyzzjcpjvcwui/Build/Intermediates/ArchiveIntermediates/Trainer/InstallationBuildProductsLocation/Applications/QA Member Connect.app/Frameworks/libswiftFoundation.dylib'2017-08-09 21:25:22.567056-0500 codesign[2529:23876] [security_exception] MacOS error: -67062/Users/ash/Library/Developer/Xcode/DerivedData/Trainer-esvcuzaerwfcyzdsyzzjcpjvcwui/Build/Intermediates/ArchiveIntermediates/Trainer/InstallationBuildProductsLocation/Applications/QA Member Connect.app/Frameworks/libswiftCoreLocation.dylib: code object is not signed at all2017-08-09 21:25:22.567234-0500 codesign[2531:23879] [security_exception] MacOS error: -670
Topic: Programming Languages SubTopic: Swift Tags:
Replies
0
Boosts
0
Views
728
Activity
Sep ’17
codesign xpc
We are having issues code signing correctly the XPC services that are deployed with our app.When checking in CLI I see the followingspctl --assess --verbose ./xxxxxx-xpc.xpc./xxxxxxx-xpc.xpc: rejected (the code is valid but does not seem to be an app)I really don't know where to take it from here. All targets are set to automatically manage sigining.There is very little on the web about examples to how to porperly codesign XPC services.We are using XCode 8.3.3The XPC services reside in Contents/XPCServicesCan anyone provide some guidance ?
Topic: Privacy & Security SubTopic: General Tags:
Replies
4
Boosts
0
Views
1.5k
Activity
Sep ’17
Reply to codesign xpc
ok so doing some further test what is happening when launching the app that is codesigned for the first time.The XPC service needs to access the main.app keychain Username and Password in order to then chat with web services. When the app is first installed there is an OS allert indicating that XPC is trying to access the Main.app keychain entry , [Always Allow] [ Deny] [Allow] . I would like to avoid this step so that the XPS service is allowed automatically and user does not need to provide input. if XPC is a target of the same app wouldd the system see it as part of it and not have to ask ?My initial thought is that the system is asking to allow the entry because the XPC services are not certified correctly but maybe there is more or something different to it ?Anyone ?
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’17
"Automatically manage signing" doesn't use the right AppID prefix
Hello everyone,I created and published an iOS application some years ago (2010) on the App Store.I didn't update it since, but I want to update it to be ARM64, so it runs on iOS 11.The project by itself was much too old (I don't remember with which version of Xcode I created it - probably Xcode 4) and upgrade to Xcode 8 doesn't work that much. So I decided to create a fresh new project with the exact same name and exact same product identifier (say it's com.mycompany.myapp), and re-added all sources of the old project.The project is configured to use Automatically manage signing, and work very well inside the simulator, and on my iPhone 6. So far, so good.But now, I try to release this update on the App Store, and when validating my stuff, it fails by saying :- On Xcode 8.3.3 : no matching provisioning profiles found for 'XXX'.- On Xcode 9.0 GM : Provisioning profile failed qualification — Profile doesn't match the entitlements file's value for the application-identifier entitlement.I tried with and without h
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
0
Boosts
0
Views
1.7k
Activity
Sep ’17
/usr/bin/codesign failed with exit code 1 cause:No such file or directory
CodeSign /Users/fanqianwen/Library/Developer/Xcode/DerivedData/iMOKO-duxwwacqnokyogbaoufeiplaswao/Build/Products/Debug-iphonesimulator/iMOKO.app cd /Users/fanqianwen/meituan/iMOKO/iMOKO export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin Signing Identity: - /usr/bin/codesign --force --sign - --timestamp=none /Users/fanqianwen/Library/Developer/Xcode/DerivedData/iMOKO-duxwwacqnokyogbaoufeiplaswao/Build/Products/Debug-iphonesimulator/iMOKO.app /Users/fanqianwen/Library/Developer/Xcode/DerivedData/iMOKO-duxwwacqnokyogbaoufeiplaswao/Build/Products/Debug-iphonesimulator/iMOKO.app: No such file or directory Command /usr/bin/codesign failed with exit code 1when linking period ,the error occur ?what should I do ?w
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
0
Boosts
0
Views
1.4k
Activity
Sep ’17
Reply to Mac App store Code Signing EXC_CRASH (Code Signature Invalid)
I can't comment on how to prevent a provisioning profile to break. But if you get your app rejected during App Store review due to a CODESIGNING crash (without having changed anything relevant), you could try the following if you let Xcode manage code signing automatically in your project:1) Delete all your provisioning profiles in your Apple developer account2) Rebuild and archive your app3) Before uploading it to the app store, you are shown the provisioning profile in use. There's a small link next to it. Click it and it shows you a cached version on your local drive in Finder. If the creation date of this one is old, move it (and all other cached provisionining profiles) away, e.g. to the Desktop folder.4) Cancel the upload to the app store.5) Rebuild and archive your app again. This time Xcode is forced to create a new provisioning profile and a new upload to the app store should now work.This fixed the problem for me, but I have no idea why the problems happen in the first place.== Matthias
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’17
Reply to Xcode 9 produces invalid Code Signature
I think I tracked down the issue. While manually checking the code signature of every framework contained in the bundle using codesign -vv, I discovered some frameworks returned an error with the following message: the sealed resource directory is invalid. Interestingly, only the frameworks built using Xcode 9 and Swift 4 are affected, older ones created with Xcode 8 and ObjC are fine. Also, the check doesn't produce an error on 10.12.Edit:It was because of the deployment target of the frameworks, but this also doesn't solve main issue.Edit 2:In fact, this solved the issue for the Developer ID-signed version, but the MAS-signed version is still broken.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
Sep ’17
Signing an app and adjust its content afterwards (signature should remain unbroken)
Currently we are signing our application with the following way:codesign --force --verify --verbose --sign certificate's name application.app/Contents/MacOS/appBinaryWe are using Mac OS X 10.8 for signing since on newer systems this usage of codesign is not working anymore.When checking the signature of the application bundle withcodesign -vvvon OS X 10.9 or later it says: resource envelope is obsolete (version 1 signature). So obviously it is version 1 signed. But even if it appears to have a deprecated signature it does not cause any harm when running the app on OS X 10.9 (or later).Now we've also tested signing on OS X 10.9 by using:codesign --deep application.app -s certificate's nameWhen checking the signature it returns: valid on disk and satisfies its Designated Requirement. And it validated all files within the bundle. So obviously this is a valid version 2 signature.Now there is one reason we currently stick to the version 1 signing: When signing the application it inherits a certain number
Topic: Developer Tools & Services SubTopic: Developer Forums Tags:
Replies
1
Boosts
0
Views
4.5k
Activity
Sep ’17