I'm extremely new to iCloud development and while I have 2 versions of my app out in the app store, it's time to bring iCloud functionality.
There are a few questions that I need to ask. These may seem really basic, but I need to understand the right procedures before continuing and I can't seem to find this information anywhere online.
My app only supports iOS 7 and I'm using the latest Xcode as well.
Question and Uncertainty
All of the tutorials I've seen cover implementing iCloud into a new
app rather than an app that already exists in the App Store and which
already has an App ID and provisioning profiles. Do I have to create a
new App ID or can I just edit my existing App ID to include iCloud and
then generate new provisioning profiles?
Also, if I generate new provisioning profiles, will this directly
impact any of my testing devices while I'm in the process of the
iCloud development?
I'm sorry but I really don't know what to do here and any guidance on taking this forward would be really appreciated!
Thanks,
You don't have to create new app id simply what you have to do is add new features to existed app id.
If you go to apple development portal--> login to your account there you will see.
Click on Certificates,identifiers & profiles--> Click on Identifiers--> Then Click on identifier to whom you want to add new feature say "iCloud"
At the bottom you will see Edit button
Click on edit you would be taken to a new screen where you can add new feature iCloud to it.
Now here are few points that you have to remember.
You would have to alter you all certificates for this identifier and then regenerate new ones. Remember all provisioning profiles,certificates need to be regenerated for this App Id.
I have done so many times further you can ask i will help you.
Related
I'm developing an iOS app in Xcode 12.2 for a client.
The client does not have an Apple Developer account yet, so I'm using the Testflight of my own account to test the app with the designer.
The app uses AppGroups, let's say I have a group named "group.com.myorg.appname".
I'm also using CoreData, and will implement NSCloudKitContainer very soon.
My question is:
Once the client has purchased a developer account, can I easily delete my version from my Testflight, and then add it to the client's Testflight, without issues?
For example, do I have to change the AppGroup identifier? And is this a problem for iCloud?
I have read this answer which contains lots of good information, but didn't allow me to be sure about iCloud or the AppGroup identifier. This was also very useful but incomplete. I've also read information about app transfert, but in my case the app is not published, it's just in Testflight, there's no publishing before moving to the client's account.
If you do not want to lose the IDs, the safest option is the transfer the app to the new account rather than deleting it. If you have push notification certificates, these would need to be regenerated on the new account. However the same goes for the App Groups. You will need to delete it from your old account to release the ID and make it available for the new one. There shouldn’t be issues doing this since it is not launched yet. https://developer.apple.com/forums/thread/70297
I'm still new to programming and this is my first ever app to be posted onto the AppStore.
I've seen a few tutorials on how to do it and followed almost all the steps. But right now I'm stuck at this point and have no clue where to go from here. I've already paid the $99 to Apple and obtained the certificates, appID and profiles...
But its all futile. I'm looking for help if possible, and thank you very much :/
edit: I managed to get it to work by downloading the provisioning profile and opening it. Which then made all these buttons available to me. It sometimes becomes greyed out again, but as long as I open the provisioning profile again, it works. So I'm guessing thats the solution.
Your image seems like you haven't add your developer account to XCODE and haven't set the provisioning profile.
XCODE > Preferences > Accounts and add your account & click download all profiles.
Then you have to follow 7th step of the below article which has the all needed informations and steps you want to upload your app to the app store. Please make sure to complete each and every step carefully. It's not hard just few clicks.
How to submit an app to app store
I'm in charge of developing and submitting the apps to the app store as the clients have sent us their apple logins. As far as developing the apps, that's been OK (I haven't submitted any yet) but in the next week I will need to submit at least three, all with different Apple IDs.
I've removed the Xcode password from the keychain and synced my certificates to the second Apple ID I have. Oh god, the mess it made with my keys, and profiles. When I did this with my own Apple Id (Xcode 3) I had to do the whole thing manually and could name keys, etc like I wanted. I entered the second Apple Id (Xcode 4) and now Xcode want's to manage everything for me. I like this but it created the keys and profiles with some stupid names. It makes it very difficult for me to sign apps with one or the other and also to backup one client's keys and not confuse them with mine. I'm afraid to enter the third Apple Id because I know the mess will be impossible to handle.
I'm open to tips, gotchas to look out for when working with multiple Apple IDs so that I can know "how it's done". And also, any other things along the way that I might encounter in the submission progress.
This is much easier if you use a separate user account on OS X for each client.
If you use one shared account for everything, then there shouldn't be any conflict if you only have one developer key and use separate bundle IDs for each application. The signing works backwards from the bundle ID - from the bundle ID it finds the correct provisioning profile, and from the provisioning profile it finds the correct distribution key.
I'm currently working on an app for someone who has hired other people to write apps using his Apple Developer account. I've been working in Xcode, and the person previous to me was using Corona SDK. The last guy was the one who initially provisioned the profile for testing, and therefore has all of the provisioning info that I need on my computer in order to allow testing from it. I know that in Xcode there's a way to export the provisioning profile and import it onto another computer to solve this problem with relative ease; is there any way to do this between Corona and Xcode so that I can have the necessary information on my computer?
The guy who was using Corona just said to delete all of the information from the account and start from scratch, but a) my boss doesn't want to do this in case he needs to push more updates on the last app that was published, and b) I don't even know if that would work. My boss is willing to pay more money if there's a way to get a second, new provisioning license, but he wants to keep the same Developer account so that all of his apps are published under it.
What is the best course of action here?
So I took over an existing iOS app from a client, that is currently available for public use through the App Store. When I was given the project in xcode, I noticed that all provisioning profiles associated with the app had expired and all were under the name of the previous developer.
So, I added myself as a developer and joined the team and code signed the development copy under my credentials. I created a new ad hoc provisioning profile for testing, and released a version through TestFlight to some registered devices. No problems. The app is greenlighted to go live.
Can someone please help me out with the release process from this point on? Do I create a third new provisioning profile for App Store release, and tie it to the code signing in XCode? Is this going to be problematic considering the version that is live now is under completely different (expired) profiles from a different developer? Is there some alternative way I need to do it through Apple? I'm trying to be super cautious here... if for some reason I release the app and its crashing because of some step I didnt take by accident, the poop will hit the fan.
You're going to have to release it under a new name on the App Store and forfeit all the ratings and reviews. Apple won't let you swap developer profiles on an existing app.
Other developers may disagree, but it looks like a huge PITA. See here
Transferring ownership of an iPhone app on the app store
The official answer seems to be NO
I didn't interpret the question as regarding change of ownership of an app.
I read the question as: I've inherited maintenance of an app and we'll want to submit an update as the same seller.
In this case, you can generate your own certificates and distribution profiles, and you can then build and submit the app.
I have done this numerous times. That is, I have inherited responsibility for an app that I did not necessarily craft originally. I easily created new signing and provisioning credentials, appropriate for the app the be submitted as the seller (not me) on their behalf.
And for what it's worth, the App Store Distribution profile is necessary, but only used when the app is submitted, so Apple can ensure that it is coming from a developer that has the right to submit it. (Remember, these profiles are signed with the same certificates used to sign your app package.) If that Distribution profile should expire or change, it has no bearing on an app already in the App Store.