Failed app upload - "The u option must have a non-empty value"

Solar2D iOS
#1

Hi all,

I finished my app last night and after some testing decided to put it on the app stores today.

It’s already available on google play.

iOS required a little more time, so I just finished about half an hour ago… my store listing is ready, I just need to upload the binary - as I did multiple times before with no issues.

This time however I’m getting a strange error that even Google seems to know nothing about.

the two errors showing up (see screenshot) in Application Loader say:

“The u option must have a non-empty value”

and

“The password option must have a non-empty value”

I have no idea what these mean, as I followed the process the same way as every time before. I’m running Mavericks, latest Xcode, latest Application loader, and latest public release of Corona (2015-2731)

Anyone got any pointers what could be wrong?

It shouldn’t be the app itself, there is no user input in the app… all the app does is send GET request to a webpage, then parse the incoming HTML, take the parsed data, and display it on the screen in some tableviews…

no usernames, no passwords anywhere…

I’m pulling my hair out :confused:

#2

I work at a company that submits builds daily to the App Store. This is a brand new error that just started popping up today. I know that doesn’t resolve the issue, but at least it provides some more context.

#3

I had this problem too, updating to xCode 7.1 fixed it

#4

Where does this error show up?

Can we get a screen shot?

Are there any errors in your console log?

What version of Corona SDK are you using?

What version of Xcode are you using?

Rob

#5

I have the same error using build 2015.2744, the error show up in the application loader, with Xcode 7.

After update to Xcode 7.1 corona says that is not supported, after build and try to upload again a new error show up, it say that my shortVersion must be different from 1.0 that it’s already in the store but this is my shortVersion CFBundleShortVersionString=“1.2”,

#6

Are you setting that in your build.settings? I wouldn’t and just set the version in the Corona build dialogs. That’s the safest thing to do.

Corona SDK currently only targets iOS 9.0. You must use Xcode 7.0. You won’t be able to use 7.1 until we add support for iOS 9.1.

Are you running Application Loader by hand or using the Corona Build dialog for uploading to the store?

Rob

#7

Yes is in my build.settings, I’m using application loader by hand not the corona dialog, and yes its true I should wait to the new dayli build, but my client can’t wait and it solve the first issue hoppely corona will upload a new dayli build soon with the fix

#8

You need to fall back to Xcode 7.1.  Please let Corona’s build dialog manage your version numbers for you and I would let Corona manage uploading it for you.  If you get this error this way, report back.

Rob

#9

Are u resolve this problem?

I got a this problem too…

where is u option and password?

please help me

#10

Hi, I have checked and I’m using Xcode 7.0.1 (7A1001).

I used Corona to build the IPA file to my hard drive, then manually use the Application loader - that’s where I get the error message (same today as yesterday).

I tried letting Corona build and send to store on its own, but unfortunately that gives me an error from Corona that I need to install “Standalone application loader” from appstore… however there is no standalone version on appstore, at least it’s not finding anything for me.  And the error window in corona even gives a link to install it, but clicking on the link actually directly opens Application loader from my Xcode, and so I don’t get anywhere in the appstore :slight_smile:

anyway, I guess my only option is to try and upgrade Xcode to 7.1 - even if the 9.1 SDK is not yet supported by corona.

I’ll do the update tonight and see if that helps - will post results in a couple of hours.

#11

I’m having the same issue. Here is a screenshot of the Application Loader’s “Deliver Your App” window and the log shown when you press “View Log”. Sorry it’s low-tech looking.  :stuck_out_tongue:

2iqbcev.jpg

726jk5.jpg

I’m using Corona version 2015.2731 and Xcode version 7.0.1

Has anyone found a solution?

 

#12

Same problem here. Corona 2731. I upgraded to Xcode version 7.1 hoping it would fix the problem.  Now I can’t build in Corona, but I was able to use Application Loader to upload my previously built .ipa to iTunesConnect.

Dave

#13

Same problem, with additional (new) error: The password must have a non-empty value. Xcode 7.0.1, day builds 2731 and 2744, no errors in the build log.

#14

Same issue here with the same error. I am not updating it to 7.1 because I don’t have another machine to build with.

What I did:

The version that does not work for whatever reason is 3.2.

Use this link and download:

3.1

https://itunespartner.apple.com/en/apps/tools

#15

agramonte, I just updated, and  you don’t need to worry.

Corona will still let you build - it only complains you’re using an unsupported SDK, but will build anyway.

I had to rebuild my app because I forgot to include one icon file and the Application Loader wouldn’t let me upload then either.

I’ve rebuilt (while having xcode 7.1), and used the application loader to upload to store…

now successfully waiting for review! :slight_smile:

#16

I’m getting the same set of errors that others here are posting. The “Eggroll Games” posted screenshots of at 7:09 AM (see above) are exactly what I’m seeing on the error page and activity log. I had no problems of this nature until today. Running daily build 2742.

#17

I successfully posted app to store by downloading Xcode 7.1 and installing Corona v 2744. Corona complains that the SDK is wrong (9.1 vs 9), but will build anyway.

#18

Same problem here (Xcode 7.0.1).

Using the Application Loader v3.1 solved the problem as @agramonte suggested.

#19

I have the same problem when uploading the build to app store using Application Loader.

My Corona build is 2015.2744. And I am using Xcode 7.0.1. And the Application loader is v3.2.

As @agramonte suggested to download Application Loader 3.1, it works now. 

#20

I’ve asked Engineering to look into this.

Rob