iTunes thinks two different apps are the same app

Getting Started Newbie Questions
#1

Hi

I have two apps. One is on the app store and the other is in development.

I’m having a weird problem building them right now. I can build either one and put it on my iPad. But when I build the other and try to install it, iTunes thinks it’s the same app and asks me if I want to replace the current one with the new one. 

I recently had problems with my profiles and deleted them from keychain and created a single new one.  This problem with the builds started after I created this new profile. 

Do I need to add both apps to this profile in the dev centre, or something like that?  

thanks,

David

#2

You must be building them with the same certificate.  If you build two apps with the same certificate, iOS considers them to be the same app.

#3

Hi - thanks for the reply. 

I’ve always been a bit unclear on this. So each app has its own unique certificate, but you can use a single provisioning profile for all your apps?

_______________

Update: I wasn’t using a wildcard profile. I think that was the problem. Anyway I have created two separate profiles, one for each app (with the same certificate) and that seems to be working now.

#4

When doing development, use a wildcard certificate and a development profile.

When deploying you’ll need a unique app certificate and a unique production profile.  

I think you got this worked out already, just commenting back.

#5

Or, do what I do…  I use one key/cert pair for distribution (serves both AdHoc and Store) and one key/cert pair for development. Then I create two app ID’s:

com.mysite.test1

com.mysite.test2

and then app ID’s for anything I intend to deploy.  Then I create an AdHoc profile for each AppID including the two test ones. I use the AdHoc one for testing and if I need an alternate version I can use one of my test AppID’s to have two copies on my device.

Rob

#6

The profile that I used to publish my app to the store is gone. I deleted it.

The next time I need to update the app, do I need to make sure to use the same certificate? Or can I just generate another certificate and profile, as long as I use the same app ID?

thanks.

#7

You can use a new certificate/key pair but you have to use the same Bundle ID.

Rob

#8

cool, thanks.

#9

You must be building them with the same certificate.  If you build two apps with the same certificate, iOS considers them to be the same app.

#10

Hi - thanks for the reply. 

I’ve always been a bit unclear on this. So each app has its own unique certificate, but you can use a single provisioning profile for all your apps?

_______________

Update: I wasn’t using a wildcard profile. I think that was the problem. Anyway I have created two separate profiles, one for each app (with the same certificate) and that seems to be working now.

#11

When doing development, use a wildcard certificate and a development profile.

When deploying you’ll need a unique app certificate and a unique production profile.  

I think you got this worked out already, just commenting back.

#12

Or, do what I do…  I use one key/cert pair for distribution (serves both AdHoc and Store) and one key/cert pair for development. Then I create two app ID’s:

com.mysite.test1

com.mysite.test2

and then app ID’s for anything I intend to deploy.  Then I create an AdHoc profile for each AppID including the two test ones. I use the AdHoc one for testing and if I need an alternate version I can use one of my test AppID’s to have two copies on my device.

Rob

#13

The profile that I used to publish my app to the store is gone. I deleted it.

The next time I need to update the app, do I need to make sure to use the same certificate? Or can I just generate another certificate and profile, as long as I use the same app ID?

thanks.

#14

You can use a new certificate/key pair but you have to use the same Bundle ID.

Rob

#15

cool, thanks.