Can't upload to Apple App Store

[srbarlow3]

I created a new store provisioning certificate using the distribution Certificate I had. I changed the stand alone settings to reflect the new certificate.
I changed the version to 1.0 and built a new standalone....comptessed it to a zip file. I used the Application Loader to find my newly created and zip'd app and proceeded to upload it.

At the end of the process I got the following messages:

Apple’s web service was not successful

Unable to authenticate the package: 835028310.itmsp

ERROR ITMS-9000: “This bundle is invalid. New apps and app updates submitted to the App Store must be built with public(GM) versions of Xcode 5 and iOS7 SDK. Do not submit apps built with beta software.” at SoftwareAsset (MZItmspSoftwareAssetPackage)

Could not start delivery: all transports failed diagnostics


What am I doing wrong...this is my first try at this...very confusing. I followed the tutorial...I thought.

Any help appreciated.

Russ

[srbarlow3]

Let me take a stab at answering my own question with an answer I hope is wrong. I spent the best part of today trying to figure out why my app was rejected from the Apple App Store. This is my first foray into mobile development since I recently retired from a career as an airline pilot and have a lot of time on my hands. I figured my inability to upload my binary must have had something to do with a bad provisioning certificate or something. It is confusing so I spent the day studying to make sure it was right. I have everything set up, app done, graphics polished, beta testing done, and iTunes Connect submission done and showing "waiting for upload". After several tries and rejections I tried a Google search on the error message I kept getting over and over (see previous post) and got a hint.

Here is an excerpt from an article Google led me to:

Starting February 1, new apps and app updates submitted to the App Store must be built with the latest version of Xcode 5 and must be optimized for iOS 7. Learn more about preparing your apps by reviewing the iOS Human Interface Guidelines.
Read the whole article here: http://www.macrumors.com/2013/12/17/app ... ebruary-1/

Having just spent $ 500 to become a commercial LiveCode developer in order to build some iOS apps I've had in mind, I feel I may have been hosed. I don't mind the three weeks I have devoted non-stop into this project,since I did learn something, but if this is true it is immensely disappointing. Can someone who works for Livecode and monitors this board tell me officially if this is true? Am I shut out of the App store even though I have an app that looks just like an iOS7 app and has had zero crashes in two weeks of beta testing? Sure I have an Android version too, but it is far less solid and polished than the iOS version.

I feel like the National Lampoon movie character Gus Griswold who drove his family 3000 miles across the country only to arrive and find out Disneyworld was closed for the season.

[Simon]

Hi Gus,
No need to worry;
http://forums.runrev.com/viewtopic.php? ... =15#p94534
That whole thread is about Apple requiring the app to be iOS 7.

Simon
Oh, and welcome to the forum!

[srbarlow3]

Simon

Are you saying that my App Store upload rejection was NOT due to Livecode? I am confused as I have LC 6.5.2, a brand new Mac with OSX 10.9.2 , Xcode 5.0.2, iOS SDK 7.0.3.. what am I missing?

Russ (Gus)

[Simon]

Hi Russ,
I was referring to that "Starting February 1..." thing only.
Someone else here may have the full answer for you. I haven't seen ERROR ITMS-900 before.

Let me check http://quality.runrev.com/
No, can't see anything related there.

Simon

[srbarlow3]

Thanks for clarifying Simon. Hopefully someone from RunRev headquarters knows. I hate to keep trying to figure why my app is not uploading until I am sure it is not some Apple policy change that is my problem.

Russ(Gus)

[Simon]

Hi Russ,
Just found this:
https://www.youtube.com/watch?v=Lyn_K_GUKUs
Feb 14 2014 so pretty sure it's still good.

Simon

[dave.kilroy]

Simon this video is a nice find, but although it was published in February this year I can see that an older version of Xcode is being used and in some screens 'September 2013' is clearly visible. That said, it is essentially correct and I've uploaded apps to the iTunesConnect in February successfully.

So Gus, in principle you should be good to go with LiveCode - however, looking at part of the text of the error message you got

Do not submit apps built with beta software

it appears that iTC thinks your app was built with a beta version of Xcode - could this be true? If so then get the new version - if not then consider reinstalling Xcode...

Kind regards

Dave

[srbarlow3]

An update. First thanks to Simon for that great video I somehow missed. I was indeed not signing the app correctly. Revoked my certificates and provisioning profiles and started from scratch following the video step by step. The only thing in the video I didn't see was in the xCode organizer window, there is no "Provisioning Profiles" in the library section. I did find my profiles in xCode through menus. Xcode-> preferences-> accounts tab-> view details button
My development and distribution profiles are listed and marked valid. So if they are created correctly xCode k

Unfortunately, after building the standalone ( I was asked for keychain access to sign the app like in the video) I got the exact same error message... Down in flames.

When I look at xCode in the App Store it says it is already installed. Do you think I should uninstall and reinstall on some chance that is the problem...I do have the latest version?

I need a break from this... Anyone know how long iTunesconnect will hold an app as "waiting for upload" before deleting it.

I AM STILL WAITING FOR SOMEONE AT LIVECODE TO TELL ME THAT THERE IS NO PROBLEM ON APPLE'S SIDE CAUSING MY REJECTION ON UPLOAD.

I would appreciate any ideas as I am spent on this one

Russ

[LCNeil]

Hi Russ,

I recently successfully uploaded an update of our Sheep Herder game to the iOS apart from the mentioned iOS 7 requirement issue. This issue is caused by a build discrepancy in LiveCode 6.5.2 and can be resolved by either using the pList method explained in this post-

http://forums.runrev.com/viewtopic.php? ... e&start=15

or by upgrading to the latest RC of LiveCod 6.6 here-

http://downloads.livecode.com/livecode/

A bug report in the issue can be found here

http://quality.runrev.com/show_bug.cgi?id=11754

itunesConnect will indefinitely hold your upload in the "waiting for upload" state so it will remain that way until the upload is successful.

With that being said, the error "Do not submit apps built with beta software." does suggest that you have a beta version of Xcode on your system and as LiveCOde builds against the version of Xcode you have installed on your system, this could be causing the issue.

Where did you download your version of Xcode from? I would also recommend removing it and re-downloading it from the Mac App store as this will rule out any Xcode related issues.

Kind Regards,


Neil Roger
--
RunRev Support Team ~ http://www.runrev.com
——

[dave.kilroy]

The only thing in the video I didn't see was in the xCode organizer window, there is no "Provisioning Profiles" in the library section.

Hi Russ, in the video they are using an earlier version of Xcode.

With the current version (Xcode 5.0.2) we need to do things slightly differently - create provisioning profiles on the website as before, and once created click the 'download' button, then find them in your 'downloads' folder and double-click them to put them into Keychain Access, then go to Xcode, preferences-accounts-view details and click the little 'refresh' button on the bottom-left of the dialog box (this button does not show the text 'refresh' it shows an arrow glyph bent round into a curve). Once this has been done go back into LiveCode (ideally restart it in my opinion) and open up the standalone settings dialog box for your app and choose the relevant provisioning profile from the drop-down list

Finally - Neil is right - the error message you are getting indicated you are running a beta version of Xcode and you will need to fix this before submitting your app. Actually, whether or not it is a beta version if iTunes Connect thinks it is beta is enough of a problem for you - maybe someone else here can suggest a clever way of fixing things but it looks like you need to do a complete uninstall followed by a full install.

Good luck!

Dave

[srbarlow3]

VICTORY! I took the LC6.6RC1 upgrade route and the upload sailed through. I was avoiding the upgrade since it was so close and I didn't want to introduce any potential new bugs... but after the frustration of the last couple days I rebuilt and tested my rather simple app for an hour on my devices and it looked good. Evidently the Beta software version comment from iTunesConnect was caused by that uploading bug because I didn't re-install xCode which I had confirmed is the latest version (I downloaded from app store a few weeks ago).

Again, thanks to the hassle this was, I understand certificates, provisioning, and code signing much better than I would have otherwise.

Now on to the Google Play store!

Thanks to everyone who helped, especially Neil Roger for THE answer, and Simon for pointing out the great RunRev video on Apple's security maze and how to beat it.

Russ

[psfakianakis]

I have exactly the same problem.

I'm using version LC 6.6

[CALL-151]

I have exactly the same problem.

I'm using version LC 6.6

Seehttp://forums.runrev.com/viewtopic.php?f=49&t=20416 for a workaround