I am getting a number of errors with the ApplicationLoader. But it looks like I have done things wrong in XCode4.2.1 and possible with certificates or profiles. Last time I submitted an App was with Xcode3.2.6. Not sure what to do here with Xcode4.2.1? thanks
After working with things a bit I have gotten to this point:
-the referencing not sure of
-code signing, I thought the process of the certs/downloading/uploading to apples sight took care of this.
And now down to this:
The remaining problems are easy to solve.
First the Icon:
Make sure you have named your icons as
icon.png
icon#2x.png
Then on the appname-Info.plist there should be a key called
"Icon Files (iOS 5)"
with a subkey
"Primary Icon"
with a subkey
"Icon files"
and 2 subkeys
"Item 0" and "Item 1"
Item 0 value should be icon.png and item 1 should be icon#2x.png
For your second problem:
You have to specify what code signing profile you want to use.
For this select your app on the item inspector and under Targets select your app again.
Then under build settings, select All and combined.
Here just scroll down to "Code Signing"
The code signing identity MUST have the RELEASE value to the same profile that has been registered on the iTunes connect (the certificate that you got which has the rights to publish etc etc)
just click on the value and you should see many provisioning profiles. If the Provisioning profile has been installed correctly (the one that can sign for release) it should also appear there, just select it.
Repeat the process for the Project configuration (Under Project -> AppName).
Edit:
if you have Entitlements defined:
If you are defining a custom Code Signing Entitlements file within
your Target > Build Settings, you might try removing that
configuration entirely and rebuilding/resubmitting. More often than
not, Code Signing Entitlements are defined unnecessarily. You only
need to specify a custom Code Signing Entitlements file if your
application is utilizing custom keychain access sharing or iCloud.
Otherwise, remove the Code Signing Entitlements configuration from all
build configurations on your Xcode project's Target > Build Settings,
the rebuild and reattempt your submission/validation.
Regarding the code signing issue:
Try following this apple guide, it explains everything very detailed
https://developer.apple.com/legacy/library/technotes/tn2250/_index.html
Especially the How do I resolve the error: Application failed codesign verification? Section.
Related
I ran into another iPhone problem again. I finished my app, and I need to test it on my phone before I submit it to the app store. But, whenever I press Run, I get an error message like this.
"The entitlements specified in your application’s Code Signing Entitlements file do not match those specified in your provisioning profile.
(0xE8008016)"
I have a Provisioning profile for development and distribution, and certificate with keys for develoment and distribution as wells as my device is listed in the portal.
I'm not really an expert at Xcode, so if you do answer, can you please explain a fix detailing every step. I know lots of other people have asked this problem, but I can't follow there answers.
Thanks in advance,
Will
Having the provisioning profile isn't the same as setting it in your build settings to run with the project. Click your Target on the left sidebar and then click the Project. Click the Build Settings tab. Under code signing, select the proper provisioning profile in each of the drop down boxes. It should build properly after that, assuming you do have the proper provisioning profile and certificate.
If you're just now testing on your phone right before you submit to the store that's a whole other problem, but I suppose you'll figure that out yourself.
Check that the build configuration you use is not pointing to some Entitlements.plist file, which in its turn might be non-existent or containing wrong data about certificate/profile pair. If that the case, the settings in latter will override anything you set in the build settings resulting in having wrong actual certificate used.
To double-check this find your configuration in the "Code Signing Entitlements" section in the Target/Project Build Settings.
In my case I had exactly the same alert when it was pointing to an "entitlements.plist", which could not be found anywhere in the project. Clearing any mentioning of this file for the target build configuration fixed the problem for me.
Since I've changed the project name (Packaging -> Product name) of my project for release on app store i'm getting the code signing error(CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 5.0'). I've deleted all provisioning, all certificate and reissued them. But it doesn't help a thing....
I'm trying the whole day but nothing helps. Please help!
Thnx
ps. I have the problem if i use the archive function. Testing on the iPhone doesn't give any problems
CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 5.0'
This error occurs for the simple reason that you don't have the "target" code-signing-identity fields set. If you just set the project-level values then they're not pushed down to the target. You need to explicitly set the "target". This solved my problem.
It's not that your profile and certificate are out of sync. As the error says "code signing is required". This indicates that you have not signed the app.
if there is error like CodeSign error: code signing is required for product type 'Application' in SDK 'iOS X.X') and if you are using Xcode 4.2 and 4.3 SDK than probably following could be a one kind of solution..If you have changed the provisioning profile or changed the code signing identity configuration due to changes while submitting the app or a new version or added a new code sign identity configuration. This error happens when the provision is not matching the bundle id & profile, you can do "Edit Scheme" (just after the run button double click on the project name), Do Edit Scheme.....follow image below
Select your code signing identity profile on the left, like archive and check the right hand side build configuration is matching & you have selected the Code Signing Identity based on the info.plist bundle setting & matching distribution profile, which is present.
I think your bundle identifier changed with the app name-change, so you will need to recover it.
Double-click the project file, then the target; look in the section called "Summary".
Change the first text field, named "Identifier", to the identifier of your app in the Developer Portal.
I got this error after a source control update, the "Active scheme" was changed to "iOS Device". Changing it back to iPhone X.Y Simulator fixed the problem.
I went through the dev portal provisioning process twice now trying to get it to work, but to no avail. I don't think it's the second half (signature is invalid), I think it actually may have to with my binary. I have a warning in Xcode that isn't helping me because I don't know what to do about it. And honestly I don't know how relevant this information even is. But it says:
"Check Dependencies: Warning: The copy bundle resources build phase contains target's info.plist"
The app runs perfectly in the simulator, and I haven't made any changes to the info.plist since I submitted the app to Apple last week. (this is an update)
To remove the warning, right click on the info.plist file and choose Get Info. Then from the Targets tab ensure that none of the targets (you may have only one target) are selected. You don't need to directly add the info.plist to the bundle. See this Apple Q&A note for further details.
Check that you are building with the correct code signing identity. Right-click on your target and select Get Info. In the build tag look for the code signing section and ensure that the correct certificate is being selected for the application specified in your info.plist.
Then do a clean build (from the Xcode menu: Build->Clean and then Build). Check the build results (Build->Build results), you may have to change the settings to show All Messages. At the end of the build log you should then see a message about a successful codesign.
My iPhone developer certificate expired. I got a new one (developer_idendity.cer) but I'm not sure how to make my xcode project and my iPhone use it.
I keep getting the Code Sign error: a valid provisioning profile matching the applications Identifier 'com.example.foo' could not be found.
What's the procedure to follow when your developer certificate expires?
I created a new "developer_identity.cer" and put it on my keychain. Then I got a new "mycompany.mobileprovision". When I try to add this to xcode via the Organizer, I see the message:
A Valid signing identity matching this profile could not be found in your keychain.
Any idea of what "signing identity" Xcode is looking for when I try to put in my update provisioning profile?
Make sure you have your new provisioning profile selected within the Project Info Panel. Click on your xcode project file on left under Groups & Files then click the Info Button beside the search box. When the info panel pops up, select the build tab then scroll down to the code signing field and select your new code signing identity there. It should work now. You might have to do it for your target file also. Basically repeat these same steps but click on the Target file under Targets in the Groups & Files pane. I hope this helps. There really is no wrong way to replace your expired certificates. Just add them to your key-chain and make sure you delete the old expired ones or there might be a conflict.
I have some source code which I had developed and later gave to another team. They signed it with their certificate and provisioning profile.
Now I have the code back and have set the appropriate values in the project properties for code signing identity (with my cert and profile). But when I run the application on a device, I get an error showing the other team's certificate and prompting that the provisioning profile does not exist.
I don't know where it is being referenced.
Can someone please help.
Thanks.
Check the Target properties, not just the Project, because it could be overridden there.
Similar thing just happened to me, in my case the "Target" settings were still set to the previous developer's certificate, while my "Project" settings were set to my new certificate. Xcode reported:
"Code Sign error: The identity 'iPhone Developer: ' doesn't match any valid certificate/private key pair in the login keychain"
Boot's answer worked for me - there are "Target" settings for signing that override the "Project" settings, which is why you may have needed to recreate the whole project, if you only changed the "Project" settings.
Change the Active SDK from iphone device to Iphone simulator. This will let you test your code on your iphone simulator. You need a cert if you plan on running your app on your device. (Maybe the code that you got was signed for device).
Under Project > Edit Project Settings... click on the Configurations menu and select All Configurations. Then scroll down to Code Signing (or type it into the search field) to verify your provisioning information, changing the Code Signing Identity as needed.
connect your iphone, open organizer, there you first need to delete the profile of your other team, and then force an add of your profile (by drag and drop or clicking the + button)
once done, change your code signing settings from the project info window and you should be okay. i faced the same problem and had to do the above to resolve it
Solution people
http://developer.apple.com/iphone/library/qa/qa2008/qa1618.html