Geek Answers Handbook

Do I need a separate distribution for each Apple AppStore application?

I'm so confused -

after a whole day's struggle, I finally figured out how to send my application to Apple through archiving and distribution from xcode.

... it was my free version

now I made my code changes, and in my pList file I changed the Bundle identifier to com.blah.mygame.pro instead of com.blah.mygame.lite

i also changed the name of the Bundle to My Game Pro instead of My Game Lite

but now I'm confused - when I click on a project in Xcode and I click "Target" instead of "Project", I cannot find my release / distribution profile! (my development / debugging profile) still exists.

If I clicked Project instead of Targets , then I will really look at my previous distribution profile.

however, in my develloper portal, I actually found that my distribution profile is associated with the identifier "com.blah.mygame.lite". I should not have done this ???

strange when I made my distribution profile earlier today, I say something like "mygame * -" or something with which I could associate it. but I just chose com.blah.mygame.lite without thinking

Do you need to have multiple distribution profiles? one for each application? that I just want Lite and pro versions?

** change:

bonus points for this:

if I only need a profile profile (and since I messed up the names of previous provisioning profiles) ... how do I rename all my distribution profiles without interfering / not interfering with my applications? he has already been submitted and is awaiting approval

* EDIT # 2:

In order, I received both applications presented with two separate distribution profiles.

however, is there a way that I can rename distribution profiles while the sending application is still using it?

I mistakenly called it "My Profile Distribution Profile" when I should have called it "Distribution Profile for my version of the game"

+1
source share
4 answers

You have two options for fixing it:

  • Use AppId as. com.blah.mygame.* . You can replace * with any number of lines and use it to create another application.

    I will not recommend this approach because the problem is that you cannot use push services or in-app purchases. You may not plan to use these services now, but if you change your mind, you cannot change your application identifier without creating a new application.

  • Create different AppId for different applications. It will be a good approach.

+2
source

It looks like you are using the same AppID for both applications. You can use only one provisioning profile for multiple applications only if the application associated with this profile has a wildcard (for example, "com.sample. *").

specified in iOS Provisioning Portal :

Part of the Bundle identifier of the application identifier can be replaced by wild-card character (asterisk '*') so that one application identifier can be used to create and install multiple applications. If the wild-card symbol is not used, the Bundle Identifier of your application identifier must be entered as the CF Bundle identifier in Xcode so that the application is installed on your device. Part of the Bundle Seed ID of your application ID does not need to be entered in Xcode. Wild-Card app IDs cannot be used with push notifications or in-app purchases.

+1
source

I hope you created an AppId with this bundle identifier com.blah.mygame.lite and created a distribution profile associated with this AppId . This way you can run or archive your applications only if it has the same AppId , like this com.blah.mygame.lite . If you want to create an AppId to run all applications, you will need a Wildcard AppId , like this com.* . And if you think that you need to run the application using the AppId com.blah.mygame.pro , then you need to create another AppId and map this AppId to another distribution profile or change the old one and download and install and use it.

+1
source

There is no need for a distribution profile for each application .... one is enough for each time, but

your package ID is identical to the one you specified in the distribution distribution profile when

you create it for the first time ....

0
source

More articles:


All Articles