There's been an error parsing your app's provisioning profile. Ensure you are uploading a validly signed IPA and try again - ios

I have a problem while trying to upload my application to firebase. This is how this error looks like:
And actually I have no idea why it happens. Could it be because of development certificates? Or could it be because of packages versions?
I have done everything according to Firebase SDK instructions, but it still doesn't work. Also, the problem is, that I just can't find any info about this error in internet. So, what is the reason of this? And how can I fix that?
PS. By the way, about .ipa file. I create it in this way.
Copy Runner.app to desktop.
Create Payload folder.
Paste Runner.app in this folder, compress it, and change .zip to .ipa

Go to your Apple Developer Profile and make sure you have an active Apple Developer subscription (your $100 (or your local currency) fee is paid), and you have the correct certificates, and signing installed onto your device, and you have a correct bundle ID linked to each of said certificates, etc. If you made any corrections, create a new .ipa file, and retry the upload process.
There is an option in Xcode under Signing & Capabilities to have Xcode manage your provisioning profile.

Related

What do i need to resign ipa files?

I was hoping that someone could explain to me the process about resigning existing IPA files and install it OTA. I'm unsure what certificates I need to have and how to sign it properly so it can be used by my own device.
I do have the following:
existing IPA file (developed by someone else)
Apple developer account
my udid registered in my developer portal
manifest.plist, ipa file, index.html referring to the files
I’ve seen several posts about this but none really worked out for me. However, I do get the message that I can install the ipa but it turns out to be grey once finished paired with the error:
cannot install ipa try again

keep old app versions submitted to store and install them on dev iPhone

I would like to keep versions submitted to the store to install them on my developer phone at a later time, is that possible? If I take that .ipa, how can I install it on my phone? Do I have another format than .ipa?
How can I build an archive of all my app store versions to install them at a later time?
I tried the solution from Rhythmic Solution, doesn't work yet ("A valid provisioning profile for this executable was not found."). My steps:
from the archives in Xcode, export one entry as App Store build
open iReSign
enter path to exported .ipa in first field
enter path to downloaded developer provisioning profile in second field
use an entitlements.plist created like here
select developer certificate
resign button
drag it on to the "installed apps" section in Xcode/devices
now I get the error "A valid provisioning profile for this executable was not found."
I think you can upload all those versions on diawi.com and get the url and save them whenever you need that version just take the respective url and install in your phone.
On other note git is a very important tool to track the versions of you code.
A while back I came across some ancient Ad Hoc builds of mine and wanted to try them out, but the technique works with AppStore submission builds, as well as developer and enterprise.
The general method is to
1. unzip your .ipa file into an .app
2. replace the embedded.mobileprovision provisioning profile (which has probably expired or does not allow installation on your device)
3. the above step invalidates the app's signature, so you resign it
4. zip the app back into an .ipa file
5. install the app via over-the-air download, drag onto the Xcode Devices window or itunes syncing (if you like pain)
iResign can do steps 1-4 for you.
If you want to duplicate entitlements, you can start here - however that can be more complicated than simply copying them across, e.g. push notifications can change from production to development and vice versa.

iOS Code Signing Identity mismatch

Whenever I try to archive my project, this is what I get :
But I never selected the Distribution Profile in Build Settings.
So I deleted every Certificates & Profiles from 'Keychain Access' and still no luck.
What might be the issue causing this? Thanks
try to regenerates the both developer and distribution certificates i think your private key was deleted from your system
this tutorial will help you to step by step solution
here
I got the same problem while archive project, so for that I had created the AdHoc certificate and its work.
Hope this will work for you.
Your Code Signing Identity section does not look fine to me. IMO you need to set your iPhone Distribution identity (instead of iPhone Developer as seen in your screenshot) in build settings for your Release config.
You cannot Archive with Developer profile/certificate (unless you do some hacky tricks).
If you really need to have a IPA with Developer profile:
Build the project. Find your xxx.app file under Products folder. Show it in Finder. Put that file under a new folder called Payload. Compress Payload folder. Now you have a zip file. Rename it and change its extension to .ipa, Finder will give you a warning but nevermind it. Now you have a running ipa signed with Developer profile.
You have to provision your XCode with a developer profile. For this, you have to follow the procedure for it. To find it, I advise you to search on line "iOS provisioning developer profile" or something like that. Actually, it is the best way to find the most up-to-date procedure.
As an example, look at this tutorial for provisioning developer profile. https://www.bignerdranch.com/we-teach/how-to-prepare/ios-device-provisioning/
You can also read the documentation from Apple: https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/ProvisioningDevelopment.html
Thanks everyone for your suggestions.
I ended up deleting every Certificates/Profiles from Keychain. I then imported the Developer Profile from another Mac and voila, it worked.

Xcode 5 Error ITMS-9000 Invalid Provisioning Profile

I've downloaded and checked all of my distribution certificates, as well as provisioning profiles. I keep getting this error message:
ERROR ITMS-9000: "Invalid Provisioning Profile. The provisioning profile included in the bundle com.-----.---- [---.app] is invalid. [Missing code-signing certificate.] .....
Read that I need to download the distribution com.----.---- provisioning profile but I only have a APPNAME provisioning profile. Downloaded it anyway and still have the same issues.
I've gone through and downloaded all possible combinations, but still can't get anything to work with application loader. Everything before has worked fine until I had to upgrade to a new MBP.
Do I revoke anything even though it's valid for another 6 months?
AppStore submission has 2 steps:
Build archive (via Xcode Archive command)
Build ipa for submission (via Organizer / Application Loader)
Each of them require certificate, provisioning and entitlements (in provisioning) for separate (but related) use.
You should use the same provisioning for the two steps. If you can’t find the exact old provisioning, you may consider re-archive the app. I don’t know why Apple splits these steps as they are highly related.
I also have this issue.
It seems to me that the key is to make sure that the "product" you are dealing with has been associated with a DISTRIBUTION provisioning profile that has been signed by the code signing identity which has the right to upload items to the app store (typically a company, or an individual developer).
However, the problem I typically face is that the *.app "product" at the foot of the project navigator list (in the 'products' group) is NOT the output of the archive operation. I can tell this from the time stamp. I do not know where the archive operation places its product. (Perhaps someone here can explain how this works).
As a consequence, what I do is I set ALL the provisioning profiles in the 'Code Signing' section of the 'Build Settings' to the DISTRIBUTION provisioning profile. I then "BUILD for RUN". This results in a *.app file in the 'Products' section of the 'Project Navigator' pane that, while it is the result of a "Build to Run" operation, is properly signed for distribution. I can tell that the *.app product is "fresh" by the time stamp.
It is then this *.app product which I compress and deploy using Application Loader.
This seemed to work - today.
(I confess that I am an amateur and I find the provisioning process somewhat cargo-cult-like, and what I write above may be a kind of infantile superstition about what works.)
I had the same error. To fix this you must do the following:
When you "click" on Build, please go to:
Product -> Build for -> Profiling
Your file (.app) are created.
To achieve this archive it should do the next step:
XCode -> Preferences ->
Choose the "locations" option, and you will get a screen with different options and routes. Select the route: Derived Data.
You take the app file, and the other file App.dSYM generated in the default folder "release-iphoneos" ... to update these two files in iTunes, you should compress these two files and upload with "Application loader".
Works fine, good luck
You should also download the certificate from Apple and also put p12 of this certificate (=private exported certificate key) file to your keychain.
This is my proble to upload my app ..
I try to more then 10 time to upload my app but not accept itune store
then i take this process and after accept my app
after then i same change as following here
In plist file are show here
then i take change to here for bundle name is wrong and "test code" space are remove
after then change is
Then I upload my app in itune and accept itune store
really this is works. thanks
Just clean all the things.
Check the developer/distribution certificate and mobile provision profile properly created, if not then revoke them from developer account and create all new one.
Remove all profiles from /Users/yourSystemName/Library/MobileDevice/Provisioning Profiles
Now, Export all certificates and keys from your keychain and Save them as backup for using them again.
Now install your developer/Distribution certificate first and install provisioning profile. And upload your application. This is tested way and should resolve your issue. Thanks.
Just clean your project files - that worked for me after receiving this error.

Building an iOS app for a client with his own developer account for App Store submission

I made an app with xCode 4.3 for a client with his own developer account.
Now i need to send him my compiled/binary app (no source code) so he can submit it under his account.
I dont know his bundle ID and neither i have his developer certificate.
Edit: And he will not supply me his developer certificate.
Can it be done?
I searched how this can be done but didn't find an answer.
Build the IPA as normal, then send it to him along with a copy of the Info.plist. He must then:
Edit the Info.plist file to include his bundle ID.
Unzip the IPA.
Replace the Info.plist file.
Re-sign the application using codesign.
Re-zip the IPA.
Submit it to iTunes Connect manually.
The way I have done this before was to log in as the client, and submit from your machine. But I guess this depends on the trust level between you
You need to have his distribution certificate (with private and public keys) and distribution profile. When you have those, you can create a compiled app for submission to Apple.
Basically, he needs to create the App ID, certificate, and profile and give them to you. If he cannot do this, you need to sign in to his account for him.
Once he has the compiled app, he can easily submit it using Xcode or Application Loader.
Build and archive the iOS app with your own certificates, then send the customer the resulting app archive (zipping up the app's archive directory, if needed). Look here for Xcode's archive files: ~/Library/Developer/Xcode/Archives/
In the archive, they can find and edit the app's Info.plist file.
Then the customer can submit the app archive from Xcode's Organizer and using their own developer account. Xcode should ask them to re-codesign the app with their own Distribution certificates as part of its upload process.

Resources