I have upgraded my license from Community to Individual, the applications created before "individual" upgrade are in "Community License". How to change the already produced application license to individual? I have deleted application and recreate but it does not accept that and gives "This app ID exists. Please select a different ID"?
The application that is published on store, has a bundle id, and you need to use the same bundle id in order to update it.
Therefore, regardless of which licence you have, you should use the same bundle id for your new version too.
But because you have an individual licence, you can use your own splash screen (not the default one).
And also, because you have an individual licence, for your new applications you can use custom bundle id.
Related
We recently enrolled in the iOS Enterprise Developer Program to be able to use in-house distribution, which significantly simplifies the deployment of the apps inside our company which is fairly big. Before joining we have thoroughly read the program documentation and we were aware that the new account would live completely separated from the standard account we use for the AppStore submissions.
What I'm unsure about is now what would be the best way to organize the two accounts in the developer portals. I'm mostly concerned with the bundle identifier since I'll be dealing with two different bundle ids inside Xcode for each application. All of our apps use iCloud and Push notifications so wildcard is not an option.
How do you organize this inside Xcode? Do you create two different targets or are you able to manage this with a new Project Configuration? What about iCloud entitlements?
EDIT
Just as an update I wanted to make clear that we're looking for the best solution to build an app for both In-House distribution and for AppStore submission.
EDIT2
Given that the enterprise program does not grant you access to iTunesConnect, where test users and product ids can be setup, is there really no way to test InApp purchases?
I'm not entirely clear on what you need, but it sounds like you want to be able to build your app store apps for internal enterprise use. Is that correct?
If you want to be able to build your app with two different bundle IDs you can create a custom build setting, and give it different values for your different configurations.
So for example, you could create your Enterprise configuration:
Then go to your target's build settings and add a user-defined build setting:
Give it a name like BUNDLE_ID, and if you expand the triangle you can give it different values for each configuration:
Next, open your Info.plist file and enter ${BUNDLE_ID} for the bundle id value:
When you compile using the "Enterprise" configuration, which you can do using a custom scheme (or via the command line build process if that's what you use), the appropriate bundle id will be used.
You can also configure the code signing/provisiong profile setting in the same way:
Once you do this, the correct push notification/iCloud entitlements will be used depending on the configuration.
We've been doing this kind of thing for a long time now. Our build server will generate enterprise and app store versions of our apps for each build, using exactly this technique.
When it comes to the provisioning portal, you will need to configure both app IDs separately for push notifications, iCloud, etc.
This does mean that push notifications must be sent separately to the app store and enterprise versions since they will not share the same bundle ID or push notification certificate.
The iCloud storage by default will be totally separate for the two versions. They may be able to access the same iCloud store (if you need this) as long as the entitlements are set up with the same team ID. But this may be a problem if you have two separate developer accounts.
I have to get a certification for my app for government customers. So there will be two (similar) apps in the app store - regular (development) version and a certified (frozen) version.
My question is - what should be different in the new app?
- new app name (e.g. My Certified App)
- new bundle id (com.mycompany.my-certified-app)
- new push certificate for the server?
- new images?
I have never submitted a lite/full version app before, maybe this type of thing is all too common.
Thanks!
You just need a different bundle ID to make two apps (they'll need to have different names in iTunes too, but the name on the homescreen / in the project can be the same).
You can create a new target for your app, and that will give you a second info.plist. That lets you specify different bundle IDs for the two versions without needing to physically copy and paste the whole project.
However you may have trouble getting this approved by Apple if both apps are identical apart from the version number / certified status.
If one app is just for testing, can't you use TestFlight or something similar to allow your customers to try the app in beta before it's certified?
I would suggest adding "- Certified" to your app name. There are plenty of examples in the iTunes store of full versions, and "- Lite" versions.
In addition to the name, it is customary to have the app icon reflect the different versions.
SeeRoboKill, and RoboKill Lite as one example.
I have a 'light'/'free' application and a full version of this app.
I want to make sure that if a user has the free version and purchases the full version,
then they will get a message asking if they want to merge the state of the free app into the full one.
Can this be done using iCloud?
This requires that both applications use the same Team ID. As long as they are setup with this same Team ID in the entitlements, they can share content.
Reference document
i just finished my iPad versions (full and lite) of my game Let's Spot It.they use different bundle seed id. (just like different apps)
then i want to work on its iphone versions. but i am not able to find the option for "generate new" bundle seed id.
Bundle Seed ID (App ID Prefix)
Use your Team ID or select an existing Bundle Seed ID for your App ID.
what happened?
I don't use high level techniques like sharing data between 2 of my apps. so can i use the same app id as other apps(which have nothing to do with this app), or can i just use the team bundle seed id? if i use team id, what should i do in my xcode project?
The last time I used my team ID as the bundle seed for a new app ID the website produced a new bundle seed, different from all previous seeds. I think this is just a confusingly labeled option on the website.
You can reuse one bundle seed for multiple apps, even if those apps do not interact. I have seen suggestions to use only one bundle seed for all your apps, just to give yourself the option to link the programs in future versions. You might want to avoid using the same seed if you are writing apps for multiple third parties, just to keep your customers' products distinct.
Whatever bundle seed you use, just enter the Bundle Identifier into the Info.plist, and add the downloaded provisioning profiles by dragging them onto the Xcode icon.
I'm making a pro version of my app and a free version, whereas i just had the free version, which is already on the app store. So how do i change my bundle ID for the pro version of my app. Do i have to do something inside of xcode?
The best way to do this is to create a new target. In Xcode, just go to File --> New Target.
This will create a separate target with a new main and info.plist. In there you can specify the app bundle ID for your pro version. Then in the target dropdown (the one you use to specify which to device to debug on) you can specify which target you want to debug and eventually build/submit for.
This creates a clean separation of your Pro and Lite builds, while being able to share the code you have already created. For each of your files, you'll need to specify which (or both) targets they need to belong to.
The answer above works; however, might I suggest you use in-app purchase to activate the paid features? That way existing users of your software will get an upgrade notification from Apple (that they should install the new version). I imagine most users interested in paying for your paid features are the same ones who are currently using your free version.