codesign

Resign iOS Application .iPA file without changing BundleId

纵然是瞬间 提交于 2019-12-22 01:20:21
问题 background: we are getting iOS apps ( .ipa ) from external developers ( their apps may be submitted in the appstore ), and they want submit their apps in our internal store just by sending their .ipa to us we are installing apps using ota, by sending plist to our endusers, itms-services://?action=download-manifest&url=[PLIST_URL] i was using some GUI signing tools such as iResign, iOS App Resigner and AppResigner, injecting custom entitlements, injection App Transport Security into info.plist

Segmentation fault: 11 when attempting to codesign .app

戏子无情 提交于 2019-12-21 07:13:32
问题 I haven't been able to find a definition for this error in relation to codesigning. I'm really quite stumped as of what to do. The error occurs when attempting to execute this command line: codesign -s "Developer ID Application: Name (ID)" -fv --deep Application.app/ System: XCode 6.2 on Yosemite 10.10.3 I've reinstalled XCode, still without any luck. This is for a desktop application. Apologies if this is a silly question! 回答1: A solution I found on the Apple forum worked for me: first, run

Unable to sign app bundle using Qt frameworks on OS X 10.10

限于喜欢 提交于 2019-12-19 09:29:58
问题 I am having trouble signing Qt Based application un OS X. I am using Qt 5.3.2. I have read various information source that contain contradictory information. Here is the content of my application bundle after I run the bin/macdeployqt Qt utility SimpleHello.app/ Contents/ Info.plist PkgInfo Frameworks/ QtCore.framework/ Resources/ Versions/ 5/ QtCore QtGui.framework/ ... same as Qt core QtPrintSupport.framework/ ... same as Qt core QtWidgets.framework/ ... same as Qt core MacOS/ SimpleHello

Xcode 5 doesn't let me export unsigned cocoa application

三世轮回 提交于 2019-12-18 21:27:14
问题 When I try to export a cocoa application in XCode 5 GM (which probably isn't anymore under NDA, if it is it will be off tomorrow) doesn't give me the option to export an unsigned application as it did in xcode 4.6 < When I pick up an archive and select export as application as shown here: In the next screen I have no chances to save it as an unsigned application, as I did before. Xcode 5: Xcode 4: Any Idea on why? is this a bug? Thanks 回答1: This seems like a bug. Even with the target signing

iOS ipa codesign on XCode 6.1 & Yosemite

廉价感情. 提交于 2019-12-18 18:51:14
问题 I was used to sign my app with the following command codesign --resource-rules=ResourceRules.plist -f -s "SIGNER_NAME" MYAPP.app After installing Yosemite and XCode 6.1 it gives the following warning: Warning: --resource-rules has been deprecated in Mac OS X >= 10.10! So I tried to remove the "--resource-rules" but now it gives the following (blocking) error: invalid resource specification rule(s) Is there any right way to codesign ? 回答1: Over on this post They answer your question. That post

Code signing error: Doesn't match key pair in default keychain

纵然是瞬间 提交于 2019-12-18 05:54:07
问题 *****Code Sign error: The identity 'iPhone Developer: XXXXXXXXXX' doesn't match any valid certificate/private key pair in the default keychain**.*** I am a member in developer profile, I have the provisioning profile installed, what must be the problem here? Code Sign error: The identity 'iPhone Developer: XXXXXXXXXXXX' doesn't match any valid certificate/private key pair in the default keychain What am I supposed to do? I already searched for a solution but still didn't find any. 回答1: This

xcodebuild - codesign -vvvv says“resource envelope is obsolete”

自古美人都是妖i 提交于 2019-12-17 21:52:44
问题 I've just updated my xcode install to use xcode 6.0.1 in order to start compiling my app for ios8 devices. For some reason I am not able to ever sign the app file correctly that is generated using the following: xcodebuild -project GrantM/GrantM.xcodeproj -configuration Release it compiles the code and appears to be fine, but running: /usr/bin/codesign --verify -vvvv GrantM/GrantM.app give me: Program /usr/bin/codesign returned 1 : [GrantM/GrantM.app: resource envelope is obsolete] Codesign

How do you codesign framework bundles for the Mac App Store?

喜夏-厌秋 提交于 2019-12-17 21:26:46
问题 After a recent submission I have gotten the following error: Invalid Signature - the nested app bundle (FooBar.app/Contents/Frameworks/GData.framework) is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information. Invalid Signature - the nested app bundle (FooBar.app/Contents/Frameworks/Growl.framework) is not signed, the signature is invalid, or it is not signed with an Apple

Codesign returned errSecInternalComponent in High Sierra

与世无争的帅哥 提交于 2019-12-17 16:57:18
问题 I tried to codesign using: /usr/bin/codesign -f -s $IDENTITY --keychain $KEYCHAIN --entitlements $ENTITLEMENTS Payload/Test.app But I get an errSecInternalComponent error. 回答1: I too got the same error from code signing. It seems to be mostly bcoz of keychain access. It is not just enough that keychain has to be in unlocked state as suggested in most of the post. I did the following steps to resolve this. Let the Login (or wherever your code signing identity is present) Keychain be in Locked

iPhone Codesign object file format invalid or unsuitable

依然范特西╮ 提交于 2019-12-17 04:21:29
问题 I accidentally deleted my target in xcode. so i created a new one with the exact same name. in the target settings i again selected the proper codesigning identity but now i can't compile for the device anymore. as soon as i want to build, i get: CodeSign build/Release-iphoneos/myApp.app ....somestuff.... /Volumes/XCodeProj/myApp/build/Release-iphoneos/myApp.app: object file format invalid or unsuitable Connad /usr/bin/codesign failed with exit code 1 I already tried to clean targets. what