I created my Xcode Project a while ago with a bundle identifier of com.CompanyName.ProjectName. But at the time I didn't have a domain. Now that I do, it is CompanyName.ca, because CompanyName.com was already taken. But, I have created an app record, and already submitted the build of the app version with the incorrect bundle identifier to iTunes connect. Obviously my Bundle Identifier is "incorrect".
My question is whether having this "incorrect" bundle identifier will create problems due to CompanyName.com being taken, and whether it is ok to submit more applications with a bundle identifier of ca.CompanyName.ProjectName instead of com.CompanyName.ProjectName.
The reverse DNS notation recommended for bundle ids does not directly translate to the kind of URLs you enter in your web browser. What matters is that the bundle id in your app's Info.plist and the one you entered in iTunes Connect match. That is how your app is identified and cannot be changed once a record for an app has been created (on iTunes Connect).
In any case there is no need to be fearful that there might be some sort of 404 error because your reverse DNS doesn't "point" to the correct domain. That is not going to happen. As for future titles, it would seem best that you DO use the correct reverse DNS notation. Just as a matter of convention.
Related
Facts:
I am trying to upload an app to the app store.
I am deploying via xcode archive distribution
I have setup an app appstoreconnect.apple.com
I have setup an ID on developer.apple.com
When I try to deploy and it getting signed I get this error
App Store Connect Operation Error
ERROR ITMS-90334: “Invalid Code Signature Identifier. The identifier “my_app_id-55554333a757b7473a4b4s7f65bd545a78w88836” in your code signature for “My App Name” must match its Bundle Identifier “my_app_id”
55554333a757b7473a4b4s7f65bd545a78w88836 is just an example of what it looks like. I have changed the real value because I'm not sure what it is
I have no idea where this number is coming from. I have searched my xcode for it, nothing.
I declare my Bundle Identifier I very explicitly just just my_app_id. Why is this number being appended to the bundle id?
Help?
Try once with auto signing instead of manual signing.
try
set Bundle Identifier has
com.example.yourapp
I am trying to upload hosted content for in-app purchases, however I have been unable to succeed so far.
I have previously uploaded around 100 in-app purchases packages for my app using Application Loader. I used to be able to upload these packages before without any issues. Now I’ve noticed that the latest version of Application Loader (Version 3.0) doesn’t even give me the option to upload hosted content (see attached)?
So instead I’ve taken the time to use the iTMSTransporter bash script instead. However when I try to upload the content packs using:
iTMSTransporter -m upload
I am getting the following error:
Package Summary:
1 package(s) were not verified because they had problems:
/Users/Cortana/Documents/iOS/Clients/AccentKit/InAppContent/854413379.itmsp - Error Messages:
ERROR ITMS-90320: "The archive for In-App Purchase 'com.accentkit.AustraliaFemale1' is invalid. The 'IAPProductIdentifier' in the ContentInfo.plist must match the In-App Purchase Product ID."
[2018-04-14 07:12:45 MYT] DBG-X: Returning 1
I’ve double checked and the value for IAPProductIdentifier on the ContentInfo.plist matches exactly with what’s setup on the In-App Purchase Product ID on iTunesConnect. (see attached screenshots) This error is making no sense to me.
Any ideas?
If there was an issue with banking and your sales contract are according to you theoretically back in effect, they may not be effectively back in effect, that is, from Apple's servers point of view.
perhaps this is a process that takes up to a week and the only way to speed it up is to call their technical support.
this is where that'll happen : https://developer.apple.com/support/technical/
I suspect it's likely that your app having been on monetary lockdown at any one point while the bank was an issue may have led into this buggy situation that apple may not have accounted for or that they have accounted for and want you to first go through their IT support process in order for them to first be able to asses that everything is in order.
cheers! :)
When I try upload my app to app store I get the following error: "Unable to lookup the settings for submission for the application at this time due to a general error". Have anyone ever get this message? Is it due to an Apple developer portal problem?
IDEDistribution.critical.log:
2017-01-06 15:32:14 +0000 The store submission configuration response failed with errors: (
"Error Domain=ITunesConnectionOperationErrorDomain Code=1614 \"Unable to lookup the settings for submission for the application at this time due to a general error\" UserInfo={NSLocalizedRecoverySuggestion=Unable to lookup the settings for submission for the application at this time due to a general error, NSLocalizedDescription=Unable to lookup the settings for submission for the application at this time due to a general error, NSLocalizedFailureReason=iTunes Store operation failed.}"
), warnings: (
), info messages: (
).
2017-01-06 15:32:16 +0000 [MT] Presenting: Error Domain=ITunesConnectionOperationErrorDomain Code=1614 "Unable to lookup the settings for submission for the application at this time due to a general error" UserInfo={NSLocalizedRecoverySuggestion=Unable to lookup the settings for submission for the application at this time due to a general error, NSLocalizedDescription=Unable to lookup the settings for submission for the application at this time due to a general error, NSLocalizedFailureReason=iTunes Store operation failed.}
I have found the solution, before uploading the app by xcode, you should create the app at http://itunesconnect.apple.com/
I had the same issue, and after playing around I realized that when updating a new version of an app, the "Bundle ID" must match the original version "Bundle ID".
Matching the Bundle ID to my version 1.0 upload solved the problem.
I got the same problem, and I realized I made spelling mistake of bundle Id...
I'm getting the same for the last couple of hours.
From the verbose.log:
Bundle ID based store submission configuration response received = (null)
Looks like a problem at their end.
I had this same problem and I went to analyze my account on Itunes, I realized that I was as a Developer. To create apps and send versions to iTunes you must also have access to the Application Manager function
In Itune connect，App info： group ID + suffix ID must be as same as your Bundle ID in Xcode Info.plist
In my case the problem was that I had specified the wrong bundle ID in my app settings in xCode. It didn't match the bundle ID I had specified in iTunes connect.
Basically this setting in xCode:
Needs to match this setting in iTunes Connect:
I have provisioning profile is installed and successfully created the ipa. The ipa will install in Dropbox without any problem, but the same ipa will give the error while installing through OTA.
I have attached the screenshot of the error.
How can i solve the issue. Any help would be appreciated.
Thanks.
The answer may depend on what OTA server you are using.
If you are running your own OTA server, like I am, then the problem may be your URL.
I saw the exact same "Cannot connect to..." error today with my personal OTA server. The problem was with the itms-services URL.
itms-services://?action=download-manifest&url=https://3ea1be94.ngrok.com/TestApp.plist
The .plist file name and the hostname for my &url= parameter were incorrect. Once I fixed them and refreshed the page, everything was fine.
If you are using your own OTA server, check that the &url= paramter is accurate and make sure it is using HTTPS. If you are not running your own OTA server, check with whoever is running it as they may be able to assist.
To proper distribute the IPA file from HTTP you should put a webpage with a Link pointing the itms-services special link for example:
Download App
This manifest file you is very simple, you need the bundleid and the URL to the IPA file
You can find an example of start from this one: https://gist.github.com/kEpEx/777df3cb1fd4bd851409
A couple of important things to consider
Valid certificate is required, and URL from Manifest and IPA should be HTTPS, (I'm not sure if self signed certificated works on this)
Take care of the manifest URL, sometimes you have parameters on the URL, you want to urlencode them or use simplier url
Sometimes you want to auth the users before allowing them to download the manifest or IPA files, take care of this, since cookies on the safari are lost when you click on this link, so if you check for session there based on the cookie you will get the "Cannot connect to" message. You will need to came out with a better aproach like generating temporaty tokens or something like that (this point took me 2 days of work to figure it out why it was failing)
I decided to try out Firebase hosting and wanted to start fresh so I deleted my one and only app, but when I tried to create a new app with the same name I was unable to due to the error:
"This Firebase URL is not available"
I can only guess this is because of caching of app names/URLs? Hopefully it will become available (unless someone else beats me to it) after some timeout? Any info from others who have experience with this issue or otherwise know the answer is appreciated!
Not sure whether this is the right place to ask although Firebase suggest coming to SO because they apparently monitor Firebase-related questions closely according to their website.
Thanks!
Once you delete a Firebase URL, it is permanently unavailable. It cannot be recovered.
During confirmation, you should see a message like this, which explains in detail:
This stems from a number of abuse vectors that are possible by misappropriating a project id that the prior owner believes is deleted and could still have apps/releases in the wild attached to the defunct backend. Since compliance requires that we purge all data related to the project, including information about ownership, there's not even a way to restore one you personally deleted.