I found that my app's bundleIdentifier is different from my App ID of iTunes. So I want to make new appID, but I can not make App ID having bundleIdentifier 'com.A.B' different from the one of App ID that I already have one :'com.A.C'. So I try to remove one I have but when I tried, it says
An unspecified error occurred.
The App ID 'ABC1D2FG3.com.A.C' appears to be in use by the App Store, so it can not be removed at this time.
So I removed all certificates and provisioning profile belonged to that AppID. But it still says same message.
I think the image is the problem. I set to upload my app, but I don't know how to cancel it.
You need to remove your app from the App Store first.
According to this document, you can only delete your app if it has at least one approved version and is currently in one of the following statuses:
Related
I have an existing app with bundle identifier com.brs.paysrc example and the app is live on store. It was created using a wildcard app id. Now i want to enable push notifications for this app. So i tried to create a new app id with b uncle identifier as com.brs.paysrc but it give some an error saying There were errors in the data supplied. Please correct and re-submit. An App ID with Identifier 'com.brs.paysrc' (example) is not available. Please enter a different string.
(I'm not sure if this'll help you...)
I had the same issue with an app our company has in the App Store.
The reason was because we have both a Developer Program (so we're allowed to submit an App onto the App Store) and an Enterprise Program (so I can make in-house copies of the app).
Our Bundle ID was registered under the Developer Program, but I had logged into the Apple Developer website and had chosen the Enterprise Program group.
In the Apple Developers website, the Identifies\App IDs didn't show our Bundle ID, because it was actually registered under our Developer Program... but, of course, it still refused to let me create the Bundle ID a second time, and, as usual, the error message gave no clue as to what the problem was.
I really hate the whole Certificates/Provisioning Profile stuff with Apple. Their error handling/reporting, when you get something wrong, is a farce. And it'll happily let you create non-working apps, deploy them to a device, then report a "Your app could not be installed at this time" when things go wrong.
Even yesterday, when I was ready to deploy a new version of the App to the App Store, I could create an Archive, the Validate said it was all fine, but then when I submitted it, it reported 3 errors in my .plist file.
Oh, and remember that your Bundle ID is stored in the .plist file and in the settings:
Make sure this Bundle ID is correct in both places!
(Sigh.)
You might have clicked it twice (I did). Check here, to see if your id is there: https://developer.apple.com/account/ios/identifier/bundle
Please give unique bundle ID, it will resolve your problem. Sometimes the same bundle ID is already used by another app. Hence this issue occurs. Try with different bundle ID it will resolve your problem.
How can I reuse the bundle ID I have created for the app ID? I even delete the associated app ID but the bundle ID still unavailable.Does it to say bundle ID couldn't be removed completely once created?
The bundle id can't be reused as exact. For example com.abc.xxx can be used only once. If you had created this app Id from one account, you can't create the same app Id from the other account. However, you will still be able to create a new one as com.abc.xxx1 like or so. There should be atleast 1 character difference in the app Id's
If you want to delete an app ID, follow these steps:
Open https://developer.apple.com and enter using your credentials.
Click on Identifiers under the Certificates, Identifiers & Profiles section.
Now click on the App ID you want to Delete.
Click on Remove next to Edit your App ID Configuration.
Again click on Remove in the confirmation message that opens.
I'm not sure what your exact scenario is, you didn't provide enough information to know that. However, I came across a similar problem which was as follows:
Some time ago I registered a new Apple Account and created an iOS app with it. I did not pay for that, i.e. the app could only ever be used for 7 days. I've never submitted that app to the app store. Nonetheless, the bundle identifier of the app was associated with that particular account.
Some time later I registered another Apple Account. This time with a payed subscription. When I attempted to sign the app I created with the first account, Xcode complained as follows:
Failed to register bundle identifier. The app identifier "xy" cannot be registered to your development team because it is not available.
and
No profiles for 'xy' were found. Xcode couldn't file any iOS App Development provisioning profiles matching 'xy'.
It seems that the bundle identifier gets strictly associated with the provisioning profile of the first account. The way to solve this is to delete that particular provisioning profile. You can do so by going to the following folder and deleting the corresponding file in that folder:
~/Library/MobileDevice/Provisioning Profiles/
Can we still use wildcard App IDs on Connect?
I have just added an app on iTunes Connect by clicking + and New iOS App. It has generated explicit IDs for all my apps.
For Bundle ID I chose "Xcode iOS Wildcard App ID - *" and typed a Bundle ID Suffix like "com.testapps.test". I filled in the rest of the form and created the app.
In member centre under App IDs, I can see an App ID with name "com-testapps-test" and ID "com.testapps.test", with Game Center and In-App-Purchase enabled. I didn't create this. I don't remember this happening last time I created and app on Connect. In fact there are now explicit App IDs for all apps I have created previously, which didn't exist before. Furthermore when I refreshed my account in Xcode Preferences, it has created and downloaded Development Profiles for all these IDs.
When I go back to Connect to look at the new App and choose About This App under More. It has Bundle ID "com-testapps-test - com.testapps.test" rather than the wildcard and suffix. If I try to change it to use the wildcard ID, I get "Your app information could not be saved. Try again. If the problem persists, contact us.".
I just got this warning when submit my app to app store, it is just warning, not error. This app was transferred from another developer account to my account before, so the prefix of the App ID is changed.. I think this should be unavoidable, but since I got this warning, what does it affect my app actually? What Keychain access would be lost?
Have you transferred the app from another developer account to your one? The previous provisioning ID will obviously be different.
UPDATE - For clarification
I have noticed that this answer is getting a lot of views so I will just edit it to include my further explanation from the comments below.
Basically the previous version of your application will NO longer be able to access keychain in order to save secure strings such as passwords (if it contains this functionality). This is because the distribution/provisioning profile it was signed with contains a different ID than the one you are using in your new distribution/provisioning profile because you have transferred your app from a previous account to your new one.
However any NEW versions of your app which are signed with the latest distribution/provisioning profile WILL be able to access keychain as normal in order to save secure data if they need this functionality because they are signed with a distribution/provisioning profile which contains the latest App ID for that app.
The warning informs you that your updated app will not be able to access items previously saved in the keychain. The old version of your app can still access and store items in the keychain, just like the new version. However the two versions cannot share information in the keychain.
In summary, all data saved in the keychain will be lost once a user updates to the new version. All information stored in UIPasteboard will also be lost.
You can see this message if:
The app was transferred to your account and you are updating it for the first time. In this case there is nothing you can do to prevent the warning (and side effects).
Your app was added to iTunes Connect before June 2011 and you recently updated the provisioning profile used by the app. Either your old provisioning profile was using a wildcard (*) App ID and the new one is now using a specific App ID, or the opposite (less likely). In the later case you can switch back and avoid the warning (choose the correct provisioning profile in Xcode). In the other case, chances are your app needs access to services like Game Center, Push Notifications (or anything that a wildcard App ID will not let you use) and you cannot avoid the warning.
If you want more details, the warning is related to the fact that App ID prefixes are attributed by Apple and cannot be changed. Check the "App IDs" section in Apple's "Certificate, Identifiers & Profiles" page (https://developer.apple.com/account/ios/identifiers/bundle/bundleList.action - you need to sign in), press on an ID and look at the "Prefix" field. You can also check Apple's Technical Note 2311 https://developer.apple.com/library/ios/technotes/tn2311/_index.html
Lastly, you might thing you could avoid the warning by changing the Keychain Access Groups (keychain-access-groups) field of your provisioning profile. This will not work as Apple will not let you have different prefixes for the App ID and for the Keychain Access Groups.
As of the stricter security in iOS 8.1.3, this is much more serious than the warning suggests; see https://developer.apple.com/library/ios/technotes/tn2319/_index.html#//apple_ref/doc/uid/DTS40013778-CH1-ERRORMESSAGES-UPGRADE_S_APPLICATION_IDENTIFIER_DOES_NOT_MATCH_THE_INSTALLED_APP. It seems like the mismatch causes a failure to upgrade to the new version. When I try to update via Xcode, it fails with an error to the device console like that in the Tech Note: “Upgrade's application-identifier entitlement string [....] does not match installed application's application-identifier string [....]; rejecting upgrade.” Trying to update via iTunes seems to fail silently.
I hope that the answer is simply “this error is simply an indication that Xcode has chosen the wrong provisioning profile,” verified as in https://developer.apple.com/library/ios/technotes/tn2318/_index.html#//apple_ref/doc/uid/DTS40013777-CH1-TNTAG65. But I last submitted my app many Xcode versions ago, and finding the right one may be a challenge.
Note the phrasing “Xcode has chosen the wrong provisioning profile”; to make sure that it chose the profile you thought you chose, click on the arrow next to the chosen profile’s truncated name in the archive verification dialog. To double-check this, submit to the App Store with a known error (I inadvertently used a missing icon), so that you see whether the warning appears.
The company I work for created an app, we uploaded it to the app and it was rejected for some Metadata. No big deal really, except that management then decided to build a new version of the app and had us delete the one submitted.
So when I go to add a new app, the same app, just a new version I get the error
The Bundle ID you entered has already been used.
The App Name you entered has already been used.
Can we undelete the other app and somehow replace it, or do we just have to wait (how long?) to upload the new one using the same Bundle ID and App Name?
The answer is to create a new bundleID, update your app, and submit a new app with a slightly chanced name to Apple. No other options as far as I have seen.
I created my iOS App ID and immediately after tried to register my app, but received the error message "The Bundle ID you entered has already been used." I tried again a few hours later -- by then, Apple had logged me out so I had to log back in.
When I tried again, it worked with no errors. Not sure if it was the time delay or the log out / back in.
bundleID is unique ID by which application can identified. If bundleID is already exist then you delete that bundleID first.
There's a bug or 'trick' on iTunes Connect that let's you use the same name after you have deleted it.
Full details here: https://hesh.am/2012/01/25/recovering-a-deleted-app-name-in-itunes-connect/