Hi there,
My attempts to build for the iOS store, are proving infertile. I keep getting the error…
I have tried many things, but non seem to be working. I do have a couple of questions tho…
- How do I change my " plist file to match your bundle ID on iTunes Connect"? My bundle ID is consistent thru Unity, XCode, and iTunes Connect. #Puzzled.
- Also, it has been suggested that my “controls” in iTunes Connect may not be set correctly. What are “controls in iTunes Connect”?
- I am using Unity 4.x, and XCode 5.x. In Unity my target iOS is set to 5.0. Can we build to anything but iOS7?
Thanks
If you change bundle id in Unity editor then you should replace your Xcode project from scratch to get this change into effect.
Thing is I did, but changed it back.
So how could that be the issue?
Also, I have just isolated what it more likely is.
The error includes a warning about my Version being 1.0, but in the Distribution build window, where I am to select the certificate (see pic), Apple is expecting Version 2.1 of an app I built a few years ago… not this one, which is on a completely different certificate, profile etc.
*note the different names of the Provision Profile and the Application.
So Apple is expecting a completely different title and version number.
I am wondering if I need to select “Ready To Upload Binary”, in iTunes Connect but I am hesitant, just in case, irt triggers off some cataclysmic event, or if it is even necessary to build the Distribution build.
So, I am wondering, how to I insure that the Distribute build is referencing the correct app and not an incorrect app in my iTunes Connect account?
I do not think this is a Apple error but users error, what you need to do is check the Distribution list within the Developer Account and.
Then check Itunes connect of the new version you are uploading, the bundle identifier, then make sure that this matches whats written in Xcode.
You got make sure the version is 1 up from old version. This all can be changed in the Xcode editor, again make sure it matches the details in Itunes connect.
I figured it out.
The issue was simply I had not set the desired app to be ready for upload binary in iTunes Connect.
Duh.