I'm using now the new Apple service for testing apps.
I know that the process to send an app for test is:
Create an ID
Create the certificates
Create an app in iTunesConnect
Archive, upload and invite internal or external test.
But not all apps that I create in my account (iTunesConnect) go to be public; because a lot of my app finish published in the accounts of my costumers.
In this way in my iTunesConnect I have a lot of: (for example)
App1 Test
App2 Test
App3 test
....
I want to delete these, is there a way?
If what I wrote is wrong, so there is another way more intelligent to follow, tell me please!
Unfortunately, you cannot delete apps from iTunes Connect unless one or more versions of the app have been approved by Apple's review team. According to their documentation:
You can delete your app if there is at least one approved version of the app
Honestly, aside from the annoyance of seeing old unused apps there, there isn't much of a problem with what you're doing. What you could do to reduce the number of "junk" apps in your portal is to re-use app identifiers after the TestFlight testing time of 30 days expires (and, of course, you'll have to clear out those beta testers).
You can Not delete it before atleast one of the versions of your app is approved!
Apparently, other people can't use your undeleted App names. I had an old one on my account that another Developer wanted to use. I got this letter from Apple:
Dear Sir or Madam,
Please include **** in the subject line of any future correspondence on this matter.
On 3/4/2016, we received a notice from **** (“Complainant”) that
Complainant believes your application named "****" infringes
Complainant’s intellectual property rights. In particular,
Complainant believes you are infringing its app name, thereby blocking
Complainant from using it on the App Store.
Related
Apple has a new policy requiring medical apps like mine to be submitted by healthcare organizations, not individual physician programmers like me. I have an app I worked on for a couple months, loaded it to AppStoreConnect, sent it out on Test Flight, good feedback, ready to release. But cannot release as individual physician. So went to my employer healthcare organization. They'd be happy to publish my app. I now have credentials within their developers account. When I try to upload my same app (rebuilt with new certificates and identifiers for organization), I can't get it to upload because Apple flags my upload as copying someone else's material -- my own material! It sees that "Cardiovascular Risk" app submitted under my healthcare organization is just like my "cardiovascular Risk" app submitted also by me under my personal developers account! If the app were already approved at least once, I could transfer it. But since never approved for the App Store, I cannot use the Transfer App process that Apple offers. Any ideas?
Best,
-- Josh
Thank you, msusare, that was the only solution. New bundle and new submission didn't work because AppStoreConnect saw my old submission and flagged it. I did not realize one could remove the entire app. Removal of the entire app from my old personal account and then posting the same app to new new account with my employer (with new bundle ID) worked. Thanks!
I am working on my first iOS app .I have enrolled my company in the Apple development program.But I didn't mention anything about the app that I am going to develop.
My app might take 6 more months to complete the coding stage. I am just wondering do I need to report my app somewhere in the Apple development program at the development stage.
Thanks in Advance
You should at least enter some app metadata, including your preferred app name into iTunes Connect. Otherwise, some other developer might take that app name first, while your app is still in development. Entering an app's name early reduces the possibility that you would then have to change the app's name (and documentation and marketing materials, etc.) at the last minute (because that app name is already in use, and Apple usually disallows exact duplicates).
I have an app uploaded on Testflight which has been expired from my developer account. I want to upload the same app to Test flight from another company developer account. Will it create a conflict?
There is no transfer option in Testflight mode.
If you haven't already read the documentation, you can find it here:
https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/TransferringAndDeletingApps.html
Key points to highlight in your case would be:
Make sure your accounts aren’t in a pending or changing state.
The App must have had at least one version that has been released to
the App Store
The last point is the most troublesome but it happens -_-
I've been struggling with an issue that, i got an apple account on which i got several apps, now the thing is, i got one app live on app store, around year back and my team deleted that app from sale on app store but that app is in my account yet, now after an year i tried to live that app again, now apple is not allowing me to publish the app because of "App name already exists", i released the app with different name but now the problem is my client needs that app live on store with same name which was deleted! now please guide me is there any way to live that app with old name or merge these two apps with previous name, because it is kind of very critical situation for me to handle.
There is an option for Transfer app on itunesconnect, what does it mean and how can i use this functionality properly?
My experience is that there is no way to do this through the interface provided by iTunes Connect.
We have in the past however sent an support request to the team that deals with iTunes Connect and they have sorted out duplicates and messed up bundle id's in the past.
When yo go to 'Contact Us' there is the option to ask a question, I would Suggest you pick 'Removing my App from the App Store'.
But explain your problem, and it is likely they will be able to help.
We have developed an app for a client which we deliver to them as an ipa signed with our dev credentials and bundle identifier etc.
When they receive it they strip off the existing credentials and re-sign it and submit it themselves to the app store.
Now there is to going to be a new version of the app that will include in-app purchase. In order to develop and test it I'm going to have to set up an entry for our in-house version of app in iTunes connect in order to create some products.
I've never done in-app purchase or set up an iTunes connect account before so was wondering if there are any potential issues I need to be aware of bearing in mind what I've said about how the app is delivered to the client and submitted to the app store.
For example:
- can I easily set up an iTunes connect account for an app that will never be released, for example I see there's a paid applications contract to agree to? (I say the app will never be released - what I mean is the exact version we deliver to the client will never be released in that form, its bundle identifier will be altered and thus will be different).
the product identifiers used during the development phase will be different than the eventual product identifiers. I already have a .plist config file in use, are there any potential issue with adding the product identifier names in there, and when the client re-signs the app they edit it to contain the actual product identifier names?
I thought I remember reading somewhere (but not can't find it) that after creating an entry for an app on iTunes connect there's a time window within which the app must be submitted. If this is correct then would the iTunes connect account disappear? If this happened before finishing the app I'd have to go through the hassle of creating a new bundle id and associated profiles and create a new iTunes connect entry to compete it?
If you have any issues I need to be aware of I'd be keen to hear.
TIA
Your plan seems to be fine, however be careful when shifting things to the product, as there are so many parts to this operation(bundle identifiers, etc...). A small mistake could set you back weeks if not months.
We have apps with IAP that we develop for other clients and they submit with their own credentials. We also have our own app on the app store with IAP. We just have to make sure that our clients set up their IAP with the same ids as we set them up with. Other than that we have not had any problems with it. Also, we fully do IAP fulfillment (downloads and IAP store display) from our servers and not from the clients.