My iOS apps are being built using a bundle identifier which doesn't match the one in prov profile.

Solar2D General Questions/Discussion
#1

Previously I had set up an app ID (eg. com.mycompany.appName) in the apple dev portal for testing, and that worked fine.  

Now, I have 3 different versions of the app, all with their own app ID, and their own prov profile:

e.g.

com.myCompany.appName.uniqueapp1

com.myCompany.appName.uniqueapp2

com.myCompany.appName.uniqueapp3

However when I try to build them, if I open them up afterwards and look at the info.plist file, all 3 will have the same Bundle identifier as the old build. 

What makes this more confusing is that I have deleted the old prov profile from my machine AND from the dev portal, so I have no idea how the new builds are being created using the old app ID.

This is causing problems as we use TestFlight to distribute our builds for testing, but

a) all three builds end up overwriting each other as their ID is the same

b) it then won’t install on the device anyway (presumably because there is some conflict).

I’m using Corona build 2014.2122, does anyone have any ideas about why this is happening?

#2

The third octet needs to be unique per app, i.e:

com.mycompany.app1

com.mycompany.app2

com.mycopmany.app3

I would also make sure to remove any app that you previously had installed (com.mycompany.appName).

#3

Ok, I’d never seen that before. In fact I’ve never seen any formatting advice other than “it must be unique”.

The original bundle ID is actually slightly different to the one my first post.

The first app was:

com.plantpot.app

and the new ones are 

com.plantpot.appName.app1

com.plantpot.appName.app2

com.plantpotmycompany.appName.app3

If what you have said is correct, then I would expect the new bundle IDs to read:

com.plantpot.appName

but this is not the case, instead they are using the original bundle ID:

com.plantpot.app

Edit: I am the topic creator, accidentally signed in with another account for first post.

#4

I’ve just worked it out, I’d set a CFBundleIdentifier in the build.settings file, which matched the old prov profile bundle ID.

#5

Is there a reason why you’re setting the bundle ID in build.settings?  I find it best to leave that to the provisioning profile you build against.

Rob

#6

I think that maybe I had to use it for a temporary fix at some point, I’m not 100% sure though.  

You’re quite right though, I don’t think it’s needed any more.

#7

The third octet needs to be unique per app, i.e:

com.mycompany.app1

com.mycompany.app2

com.mycopmany.app3

I would also make sure to remove any app that you previously had installed (com.mycompany.appName).

#8

Ok, I’d never seen that before. In fact I’ve never seen any formatting advice other than “it must be unique”.

The original bundle ID is actually slightly different to the one my first post.

The first app was:

com.plantpot.app

and the new ones are 

com.plantpot.appName.app1

com.plantpot.appName.app2

com.plantpotmycompany.appName.app3

If what you have said is correct, then I would expect the new bundle IDs to read:

com.plantpot.appName

but this is not the case, instead they are using the original bundle ID:

com.plantpot.app

Edit: I am the topic creator, accidentally signed in with another account for first post.

#9

I’ve just worked it out, I’d set a CFBundleIdentifier in the build.settings file, which matched the old prov profile bundle ID.

#10

Is there a reason why you’re setting the bundle ID in build.settings?  I find it best to leave that to the provisioning profile you build against.

Rob

#11

I think that maybe I had to use it for a temporary fix at some point, I’m not 100% sure though.  

You’re quite right though, I don’t think it’s needed any more.