I'm confused by the dev and dist cert. I got one app in the store, but I named my certs after my first app. Was this a mistake?
I'm ready to go on my second app. But XCode is selected the dist cert with the old app name on it. It built without error. Though I named it wrong, will it still work? XCode is automatically picking this cert for me.
Is this right? You need a new app ID for each app so you can 1) put in plist, 2) put in code signing section on Build tab of Target info, but you don't need a new dev and dist cert for each new app.
Therefore is this right too? For each app you develop, you only need your original dev and dist cert, but a new app ID for each app.
This is so obscure! I wish apple had done a better job!
All of these issues are fixed in the current (as of 7/2011) new processes Apple has in place. The Provisioning Portal cleaned up this mess and now it's not too hard. Still step-laden, but 1000x better than it was before.
Related
I have some trouble with Xcode11, and anual renew certificates. So I'm lot of lost and have no response about my trouble.
So I add a new question, perhaps more simple:
What happen if I remove ALL trace of certificate, profile, if I clean all. Can it affect my current production app, or can i still update ?
I suspect conflict from lot of certificate test, but no other idea.
Thank you
Let's say you go to the developer center and revoke/delete all certificates and profiles. And on your computer you delete all certificates from your Keychain, and you delete all profiles from the MobileDevice folder.
Then if you have an app on the App Store, it will continue to work; users can still download it. But you will not be able to submit any updates to it and you will not be able to run any projects on a device.
You could then fix that by obtaining new certificates and profiles, which you can probably do automatically; in fact, if you try to run a project on a device, it will likely all happen automatically.
I have a tricky situation here. I have an app, where the previous developer is not available; so i can't get get an export of the certificate idenetifiers
The app already has an approved version on appstore
I would like to release an update, but as i mentioned i do not have any access to previous developer
I have so much confusion right now...
Can i remove the existing bundle in itunesconnect and recreate a new one with the same bundle id? So that i can submit a new version with the same bundle it (create certificates and stuff from scratch)
If at all i can remove, will this effect existing app in appstore?
Is there any way i can create new provisioning profiles for the existing certificates? (I tried, with the message missing private key)
Any suggestions are highly appreciated
Thanks
I'm going through a similar situation myself, some research landed me on an Apple document that reads:
"
Important: Re-creating your development or distribution certificates doesn’t affect apps that you’ve submitted to the store nor does it affect your ability to update them.
"
So, it seems to me that I can recreate the certificates and the provisioning profiles without impacting the current App or its future updates.
Here´s the link : https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html#//apple_ref/doc/uid/TP40012582-CH31-SW6
I try to upload my Mac App to the App Store, but I am in trouble with iTunesConnect since one week by now. I definitely need your kind help.
I read the Apple documentation a couple of times and asked google for a solution. I tried new Certificates and provision Profiles, a lot of build settings and - yes - I even moved to a new mac with a fresh Xcode on it. No success so far.
Here is my story: I build and run my app successfully. I subscribed to the Mac Developer Program and configured my project to sign the application for a App Store submission.
I made an archive and validated it successfully.
Then I exported the Binary like the documentation suggested and all tests passed.
Then I uploaded the archive to iTunesConnect. The archive got processed and then... I got the little triangle near the build and as I clicked onto that build, there is absolutely no information all.
Sorry I moved to a german Mac and didn't change the language to English by now
After nine builds and one week of reading and trying I have absolutely no idea how to solve that problem.
Thank you very much for every new thought.
* UPDATE *
I removed the provision profile and created a new one. Then I built a complete new Project with the same ID and uploaded it as a new build number. Again, the pre-release tab is empty.
These are my code signing settings:
I've cloned an app (the app was made initially by someone else, they've added me as a collaborator as I took the job, but for more security, I've cloned the app myself by using the new clone feature) and renamed the new project, but it's still deploying to the old app, even though I've removed myself from its collaborators. I haven't changed anything on my computer and (presumably) because they have the same name, parse develop myappname and parse deploy [seemed to] work.
Just after I've posted the question, I've found the answer: it was the app key/master key pair. When I cloned the app, my app has been assigned new keys, but ~/config/global.json still had the keys of the old app. I've changed the app key and the master key in that file with the new keys in my Parse settings, and it worked. It's now deploying to my new app. Wish it updated automatically, though.
One of the apps I've developed is submitted and approved to the appstore.
Because of some big changes and a more generic code I created a new XCode project for this app.
The problem is when trying to install the same app (based on bundle identifier) from the new XCode project, it quits with a crash. If I try to install again (Build & Run/Debug) from XCode, it seems to successfully overwrite and run. So it seems the first time there are some merge / overwrite conflicts. A second install, over the failed first attempt makes it work.
I wouldn't want this to happen with app updates downloaded from the store.
I've read that the idea is not to build from XCode, but use an Ad Hoc Build through iTunes instead. This would simulate a more natural end-user process. I've tried this, but somehow it won't sync / overwrite the existing app from the appstore (no errors, the app is just not changing).
Does someone have a hint on how to solve this?
Any help on this matter would be greatly appreciated!
I run into this problem all the time. I use one Developer Profile for all my dev work (and thus, one bundle identifier).
You have to delete the old App from the phone, and do a Clean Build.
These are similar problems. (1) (2)
As it seems working with an Ad Hoc build through iTunes does work.
Yesterday I double-clicked, but never got the iTunes message warning me of an older version existing in my apps and whether I want to replace it.
Dragging the .IPA into the iTunes app section did give me this message. Telling it to replace and next syncing works okay. iTunes sync status bar displays the message "YourAppName Updating". Afterwards launching it works fine with stored data intact.
The flow described here worked for me:
How to test an iPhone application update