Search results for

codesign

3,110 results found

Post

Replies

Boosts

Views

Activity

Production OS X app won't run on some systems: "unidentified developer"
I was putting the final touches on my production build scripts when I discovered that the apps I'm producing won't run on some machines.My final build target builds that products for distribution (DEPLOYMENT_POSTPROCESSING=YES, Target=Deployment). These are then packaged in a disk image.I can open the disk image on my computer and run all of the apps. Note that some of the app bundles include privileged helper tools that must be correctly signed, and apparently they are because they get installed.I then copy the disk image to three other test systems (OS X 10.7, 10.9, and 10.10) and try to run them there. None of the apps will launch. I get a message that they are from an unidentified developer. (Note that all of these systems, including mine, only allow App Store and identified apps to be launched.)If I perform a codesign --verify or codesign --display -r- and dump the signing information for the apps, everything looks like it's been signed. (If I do the same to an Apple app like Numbers, I
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
6
0
1k
Jul ’15
codesign: "A timestamp was expected but was not found"
Hello,My CI builds are failing regularly since July 1st with this codesign error: A timestamp was expected but was not found..The Mac app has a few frameworks which are properly signed, and sometimes it gets through the signing process but fails at a seemingly random code signing command with this error.I have checked and the signing certificate (Developer ID) expires in 2017. I also made sure that the CI servers had their time set automatically using the time.apple.com servers to prevent clock drift.Short of disabling timestamps with --timestamp none in the codesign command, is there anything I can do? Am I tied to Apple's timestamp servers' whims?Thanks for any insight,Philippe
Topic: Developer Tools & Services SubTopic: Xcode Tags:
7
0
10k
Jul ’15
Xcode 6.3.2 code signing issues
When working on a project, Xcode randomly gave me an error when building the project with or without codesigning enabled. I don't think this is version specific, because i've heard of other people having this issue in Xcode 6.3. I get the error as follows: invalid or unsupported format for signatureIn subcomponent:It also includes that it failed with exit code 1. This happens to all of my projects regardless of how they're set to codesign. If anybody knows of a fix, I would appreciate instructions on how do to so.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
0
0
1k
Jul ’15
Updated to Xcode 6.4 and code signing broke
Ok, so, first off, I apologize for my attitude but I spent many hours going through the nightmare of getting dev and production certificates working for my app only a day ago and everything broke just because I updated my Xcode from 6.3.2 to 6.4 so I could test an app on a device updated to iOS 8.4. I'm pretty annoyed and ******.Anyway, as soon as the xcode update was complete, my code, which was working perfectly, now gives these errors when I try to run on my phone (8.3) or ipad (8.4) but works fine when put on the simulator:Check dependenciesCode Sign error: ad hoc code signing not allowed with SDK 'iOS 8.4'CodeSign error: code signing is required for product type 'Unit Test Bundle' in SDK 'iOS 8.4'I did not change anything with the signing but have since tried every combination of the dev and production certificates I have. I am trying to test on my devices and need to continue to push new builds to beta testers on TestFlight but I'm completely stuck...
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
4
0
3.8k
Jul ’15
Reply to xCode stuck on "signing product"
I'm experiencing the same hang when building an project that has an app target with one embedded cocoa touch framework, which is also built as a dependency. I'm running the beta 2 of Xcode 7 and Server 5.1 with Xcode server on the same MBP box which is running 10.10.4 release. The raw log file shows what happens after the hang:CodeSign /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/DerivedData/Build/Products/Debug-iphoneos/SpotfireFramework.framework cd /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/Source/Spotfire/SpotfireFramework export CODESIGN_ALLOCATE=/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbinSigning Identity: iPhone Dist
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’15
Reply to Xcode Server Sigining Product
I'm experiencing a similar hang when building in Xcode server. For me it hangs in step 4 of 9 Signing product. I'm running the beta 2 of Xcode 7 and Server 5.1 with Xcode server on the same MBP box which is running 10.10.4 release. The raw log file shows a similar problem to what you are reporting after the hang:CodeSign /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/DerivedData/Build/Products/Debug-iphoneos/SpotfireFramework.framework cd /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/Source/Spotfire/SpotfireFramework export CODESIGN_ALLOCATE=/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbinSigning Identity: iPhone Distribution: TIBCO
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jul ’15
Reply to OS X Server Continious Intergration Error CodeSign
Finally I figured it out. Since the codesign and provisional file work properly on your local XCode, the cert. & provisional files should work. So you need to commit and check in your local copy to remote repo. My codesign error was from, I guess I need to make sure the codesign & provisional setting with XCode needs to be corretly set in Project & target.Secondly, follow this instruction, https://github.com/heleny/xcode-continuous-integration. Read the FAQ part. bascially, copy your local provisional files to the folder of your XCode Server
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jul ’15
Reply to xCode stuck on "signing product"
I just installed beta 3 of both Xcode 7 and Server 5. The same hang occurs - no change in behavior:...CodeSign /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/DerivedData/Build/Products/Debug-iphoneos/SpotfireFramework.framework cd /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/Source/Spotfire/SpotfireFramework export CODESIGN_ALLOCATE=/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin Signing Identity: iPhone Distribution: TIBCO Software, Inc.Provisioning Profile: Spotfire Mobile In House (0f82676b-7dd8-4a63-9e8f-da7a79388a21) /usr/bin/codesign --force --sign E000B219A7751C3EA5A4837FFD4B5CF312F4F4AF /Library/Developer
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’15
Reply to Xcode Server Sigining Product
I just installed beta 3 of both Xcode 7 and Server 5. The same hang occurs - no change in behavior:...CodeSign /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/DerivedData/Build/Products/Debug-iphoneos/SpotfireFramework.framework cd /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/Source/Spotfire/SpotfireFramework export CODESIGN_ALLOCATE=/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin Signing Identity: iPhone Distribution: TIBCO Software, Inc.Provisioning Profile: Spotfire Mobile In House (0f82676b-7dd8-4a63-9e8f-da7a79388a21) /usr/bin/codesign --force --sign E000B219A7751C3EA5A4837FFD4B5CF312F4F4AF /Library/Developer
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jul ’15
Xcode CI codesign issues
I'm using the latest El Capitan, and Server Beta 3 with Xcode Beta 3.The selected Xcode is configured with the proper team account that has the codesigning certificate.This was from importing a devloper profile.I also added and selected the corresponding team on the CI config screen in the Server.app.Building with the Xcode that is selected, code signs properly. However when the bot runs, it fails saying it can't find the identity.Any ideas on why the Xcode the server is configured to use code signs properly, but the bot cannot?
Topic: App & System Services SubTopic: Core OS Tags:
0
0
324
Jul ’15
Watch app spins and crash, only on real device
Hello there.I am attempting to write a simple app with Watch OS 2 beta (Build: 13S5293f), iOS 9 beta 3 and Xcode 7.0-beta3.Currently the content of app is no more than the template created by Xcode.The app runs fine on simulator.On real device it can be installed without error, but is not starting. A few circles are displayed for 20~30 seconds and the app list get shown again.I also found items like these in Xcode's device log:Incident Identifier: 961A7AE2-A32D-4FEF-B68B-9A303033A151 CrashReporter Key: fc1b885080eb08a7a9be274095215827a27a7992 Hardware Model: Watch1,1 Process: watch-demo WatchKit Extension [310] Path: /private/var/mobile/Containers/Bundle/Application/1698441D-EC36-4202-B4BE-32F8D0AAE097/com.example.watch-demo.watchkitapp.app/PlugIns/watch-demo WatchKit Extension.appex/watch-demo WatchKit Extension Identifier: com.example.watch-demo.watchkitapp.watchkitextension Version: 1 (1.0) Code Type: ARM (Native) Parent Process: launchd [1] Date/Time: 2015-07-15 12:11:13.13 +0900 Launch Time: 2015-07-15 1
Topic: App & System Services SubTopic: Core OS Tags:
5
0
1.4k
Jul ’15
Reply to Correct way to sign an embedded app bundle in Xcode 7?
Well, I've made no progress on this. In the What to Sign section of the Code Signing Guide, it states:If your application consists of a big UI part with one or more little helper tools that try to present a single face to the user, you can make them indistinguishable to code signing by giving them all the exact same code signing identifier. (You can do that by making sure that they all have the same CFBundleIdentifier value in their Info.plist, or by using the -i option in the codesign command, to assign the same identifier.)However, in the man page for the codesign tool, the description for the -i/--identifier option says It is a very bad idea to sign different programs with the same identifier (emphasis theirs).Ignoring the codesign man page, I set up the two embedded helper apps to be signed with my Developer ID: * and added the --identifier com.qrecall.client so both embedded apps will be signed with the same identifier as the parent app bundle.Yet, the ValidateEmbeddedBinary bu
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’15
Reply to iCloud entitlements
In case anyone runs into the issue, the fix is to only have the entitlement for key value storage in the app's entitlement file, ignoring anything else Xcode wants. If you let Xcode handle things, it also adds an entitlement for containers and document storage. At compile time, codesign won't be happy because it wants to see that entitlement in your provisioning profile, and the only way to fix that situation is to add it to the app ID on the portal, then invalidate and regenerate provisioning profiles, etc.I deleted the containers entitlement from the app's entitlement file, and ignored the red flag in Xcode with the fix note. Set up that way with just key value entitlements, everything is fine. If you let Xcode fix this, it goes the whole 9 yards and messes up a lot of stuff it shouldn't, creating major headaches up and down the chain. The first time I was stupid enough to click the fix button, and that is what made a mess. It added container entitlements to my app ID for me, required at least one
Topic: App & System Services SubTopic: iCloud & Data Tags:
Jul ’15
Reply to What is required to register for CoreWLAN events?
I'm not in a position to reverse engineer other developer's software on your behalf, or to comment on App Review policies, but my experience is that apps that are doing seemingly-impossible things fall into one of three categories:they're breaking the rules and App Review hasn't caught them yet (A)their marketing material is being economical with the truth (B)they are grandfathered in from a previous world (C)My guess is that point C applies in this case, although I'm not in a position to confirm that.Of course, you could do that easily:buy the appdownload itdump its entitlements$ codesign -d --entitlements :- /path/to/some.appI can say that there is no supported way to do Wi-Fi scanner from a sandboxed app, and that Mac App Store currently requires that all apps be sandboxed.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: Networking Tags:
Jul ’15