codesign

iPhone Codesign object file format invalid or unsuitable

随声附和 提交于 2019-12-17 04:21:11
问题 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

self sign my code and test on iphone in xCode

你离开我真会死。 提交于 2019-12-13 05:19:38
问题 I have created iphone project. I want to test it on my iphone. I don't have an account on itunesconnect so I'm unable to load a certificate to sign my code. I've created my own certificate (Keychain Access->Certificate Assistant ->Create Certificate). But I could not sign my project with it. xCode can not see my self-signed certificate. How can I sign my code to test it on my device without itunesconnect account? 回答1: A certificate is not a provisioning profile. You need a provisioning

How to build MacOS app with hardened runtime in AppBundler

纵饮孤独 提交于 2019-12-13 03:18:46
问题 I am using AppBundler plugin in gradle to build my Java app. Now to have my app notarized, Apple requires the app to be built with 'hardened runtime' option. Does anyone know how to achieve this? 回答1: I added the following entitlements when signing my app and fixed the problem. <?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>com.apple.security.cs.allow-jit</key>

macOS notarization error: “The signature algorithm used is too weak”

北城余情 提交于 2019-12-12 12:17:03
问题 I wonder if anyone's familiar with this error which only happens when I upload my apps to Apple for notarization: "AppName.zip/AppName.app/Contents/Resources/EWSMacCompress.tar.gz/EWSMacCompress.tar/EWSMac.framework/Versions/A/EWSMac83886082" "The signature algorithm used is too weak." Additional info: -I've been signing my apps for years with no issues. The error only happens when sending the apps for notarization. -I submitted a bug back in November 2018, provided Apple all the info they

Sign java applet so that it works on OS X 10.8 Mountain Lion and Windows

℡╲_俬逩灬. 提交于 2019-12-12 06:37:16
问题 I develop an Java Applet that needs to break out of the sandbox so it is signed by a certificate from a trusted CA (Thwate). This has worked well on OS X, Windows and Linux. Now with OS X 10.8 (Mountain Lion) I have this issue: OS X 10.8 Gatekeeper and Java applets It seams like OS X 10.8 require a signed applet to be signed with an Apple Developer ID Certificate. My question is: If I change so that the applet is signed by a Apple Developer ID Certificate will this also work on windows/linux

What is the “identity string” of my certificate (mac + codesign utility)?

混江龙づ霸主 提交于 2019-12-11 19:47:16
问题 I'm gonna say this right away: I have no idea what I'm doing here. I am not a mac developer. Here's the scenario: I have an installer (.pkg) that my boss wants me to sign. I have a certificate, issued by Thawte; which I've imported into the keychain program (and set it to be trusted for everything). In package maker, under the configuration tab, there is a label that says "Certificate", and directly next to it another that reads "not supported". Well, great. So, codesign; says it can't sign

Failed to sign Mac OS X app

£可爱£侵袭症+ 提交于 2019-12-11 07:24:21
问题 I am running this lines of code to sign my app of Java application on Mac OS X - #!/bin/sh export CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/usr/bin/codesign_allocate" codesign -s "my name" my.app codesign -v -v my.app && echo my.app is Signed Successfully! I have written these all lines into one sh (SignApp.sh) file and running this sh file on creating app successfully to sign in my build.xml file as - <target name="SigningApp"> <exec executable="/bin/sh"> <arg value=

XCode doesn't honor the “iOS Distribution” Code Signing Entity setting

早过忘川 提交于 2019-12-11 06:28:36
问题 I want correctly understand the Code Signing Identity setting: I want to use the automatic setting in Xcode and not specify a specific identity. The automatic setting has 2 choices: iOS Developer and iOS Distribution. Based on which one you use, it's supposed to switch to choose a developer or a distribution signing identity from your keychain. I have my build settings configured as follow, in order to use an "iOS Distribution" identity on build: When I Archive my app (the Archive scheme is

IBM Worklight/MobileFirst 6.x/7.0 - “Code object is not signed at all.” error with buildtime.sh script

吃可爱长大的小学妹 提交于 2019-12-10 16:44:23
问题 I am having an error when uploading my Worklight Application into iTunes. The application validation fails with the following error: Invalid Signature. Code object is not signed at all. The binary at path [MyApp.app/buildtime.sh] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any

Codesign returns unknown error after “replacing existing signature”

北慕城南 提交于 2019-12-10 16:33:57
问题 I am trying to build a Xamarin iOS app using xbuild on Jenkins. Sometimes the build fails during the codesigning process with an unknown error -1=ffffffffffffffff and sometimes the build succeeds. The provisioning profile is stored in a separate keychain jenkins.keychain (not the system or login keychain) that is referenced by Jenkins through the Keychains and Provisioning Profiles Plugin. This is the console log of Jenkins: Target _CodesignAppBundle: Codesign Task CodesignAllocate: