provisioning profile problem? - iphone

i am running my apps with different provisioning profiles.(I am creating one
provisioning profile for each application an running in device). but i want to
run all applications in my device(without overwritting previous apps) with only one provisioning profile.I hope , it is possible.when we set apple id only in plist file as "com.myappleid.identifer(123145^&)" identifier will come uniquely automatically.can any one give simple tutorial to create the provisioning profile?
can i use my previous development certificate for that provisioning profile?

I think you want a wildcard provisioning profile. If all your apps start with the same identifier, e.g. com.myappleid.App1, com.myappleid.App2... then you can create a provisioning profile with the identifier com.myappleid.* which would match all of the above.

Related

Submitting iPhone App To App Store, Proper provision profile

We are in the process of submitting an iphone app to the app store. We've tested it using an adhoc distribution provisioning profile, however I was wondering if I need to create a separate provisioning profile for the app store.
On the distribution tab in the provisioning area, it enables me to create a distribution provision profile for the app store. Do I need to build the app with that in order to submit it?
Ad hoc would will not work. For me dealing the certificates and provisioning profiles is a very annoying experience.
This is what I needed to do to submit an app:
In Developer under iOS Provisioning Portal I needed to generate 4 certificates and download the WWDR intermediate certificate to be able to submit my app to the App Store:
Under Developer Certificate section (link) generate a Developer Certificate. Also Make sure that you have the WWDR intermediate certificate installed, if in doubt download it from there.
Under Developer Certificate section (link) generate a Distribution Certificate (This is not that will show up in Xcode!)
Under Provisioning section (link) generate a Development Provisioning profile certificate
Under Provisioning section (link)generate a Distribution Provisioning profile. THIS WILL SHOW UP IN XCODE AS A DISTRIBUTION CERTIFICATE!
After that I was able to select the iPhone distribution profile generated at 4. Also make sure that your target and project settings are the same.
I hope it helps
Yes, the adhoc will not work, you need to rebuild / archive with the profile made for distribution app store
Back in 2009, I did use my ad hoc provisioning profile to submit the app to the store:)
But looks like things have changed since then. I guess the answers say it will not work because the application validators detect this?

Upload IPhone app to device instead of other app

So I'm not that familiar with the process of Provisioning profiles and certificates.
Currently I have one app I'm developing that I can upload to my device.
Now, for testing reasons, I want to write a very simple app and to upload it to my device as well. The thing is, is that I don't want to configure another app in iTunes connect and provisioning profiles, so I thought maybe it's possible just to change the bundle identifier of the second app to be the same as the first.
However, in XCode I get the following error :
"Code Sign error: The identity 'iPhone Developer' doesn't match any identity in any profile"
Any way to make this happen?
If you set the bundle identifier of the 2nd app to be the same as the 1st, the 2nd app will replace the 1st one on your phone.
If you want the ability to have both apps installed at the same time, you need a new app id.
But you don't want to create a new app id for each test project.
The idea is to recreate the Team provisioning profile available for the Company developer program (I guess you subscribed to the individual developer program).
Create a new app id with bundle identifier set to *
Create the provisioning profile associated to this app id
Download and install this generic provisioning profile
With this wildcard profile, you will be able to install any test application.
Please request a certificate to apple through your paid developer account, generate a provisioning profile and install this in mac as well as in your device. then choose your provisioning profile and build and run your app through this provision.then it will install in device. There are details in developer.apple.com regarding to this. If you feels confusion please mail me sandeep.kniit#gmail.com. i will reply you asap.

Provision profile problems

My app's provision profile expired 2 days back, i created a new one and now it gives me the error:
Code Signing Entitlements Do Not Match Provisioning Profile
EveryThing is same,jus the profile name is changed..
Anyone here knws wat's the problem??
It can happen that you have not created your provisioning profile for the same application id.
The easiest is to create a provisioning profile for the app id "*" (in case you are not using special things, like push) - and you can use this provisioning profile for every application of yours.
Also - you can delete your provisioning profile from the apple developer website and your xcode organizer, and you click on the refresh button in organizer then xcode will talk to the apple dev website and download a new one for you.
Hope this helps, Moszi

How can I update my App in the App Store if the Distribution Provisioning Profile expired?

I want to update an existing App in the App Store, but the profile I used expired (I'm not sure, if it has something to do with the corresponding certificate which also expired..). Since Apple tells me in the How-Tos:
Use the same Distribution Provisioning
Profile to build each new version of
your application
I don't know, what to do. Can anyone help?
The important part is keep the same bundle id.
If your provisioning profile has expired or you has to generate another certificate, it doesn't matter.
Get anew version of you provisioning profile, build your app and it should be fine.
If the profile is expired, simple renew it or generate a new one. I did it yesterday, my dist profile was expired and I simply deleted it and generated a new one.
Once a new one certificate is generated, download it, delete the old one from your keychain and add the new one.
After that, try to build your app. (Sometimes restarting Xcode is required)
Every profile and every certificate will expire. As long as the developer account is still the same, simply creating a new distribution cert should do the trick.
You need to keep exactly two things the same: the enrolled iOS Developer account you use, and the Target Identifier Property in Xcode (becomes the Bundle Identifier in the app). Do that, and the result will be an update to the same app in the App store.
Everything else you can renew, recreate in the portal, install on a new Mac, etc., including App IDs (wildcard on not) created in the portal, Developer or Distribution certificates, and provisioning profiles in the portal, installed in Xcode or on the iDevice. You can also change the Bundle display name (under the icon), the Product name, the Target name in Xcode, and maybe even the name of the app as it appears in the App store (if it's not misleadingly different).
Renew your certificate and provisioning profile at the iOS Developer Portal.

Is there any advantage to using a wildcard provisioning profile?

I remember before reading that if you used a wildcard provisioning id (eg net.nevan.*), you could have easier sharing of information between your apps. Now, many things require a provisioning id for each app to be unique (iAds, notifications, in-app purchase). Actually, looking at my apps on the app store, they are all using unique ids.
Is there still an advantage (other than convenience) to using a wildcard id for provisioning profiles?
The biggest plus is that if you don't need unique provisioning profiles, you only need to make one once, and when it expires, you only need to refresh the one provisioning profile. If you've got 10 applications each with its own development and distribution provisioning profile, that's 20 provisioning profiles you have to keep up with if you're actively developing all 10 applications. Plus another profile each if you want to do any ad-hoc building for beta testers.