[FranciscoValenzuela]

Ok, am going to re-do the whole process, I will delete the certificates in member center and I will rebuild the csr from Digital Signing MobiOne Utility, then generare certificate and build app, just one question, does the information company has to be exactly like the member center account?, fill all fields?

[support-michael]

>Ok, am going to re-do the whole process, I will delete the certificates in member center

If you have a valid pk/cert/appstore-profile or p12/appstore-profile then use it to build your itunes app with. You should not need to regen this data unless you loose/forget your pk or p12 password.

[Paul_paul]

If your app is going through the build process with no errors there should be no need to ‘redo’ your certificates. If you can install the app to your device using the ad-hoc profile there is no need to ‘redo’ your profiles.
If you re-build the app with the app store profile but it refuses to upload to iTunes Connect I would guess there is an issue with the app builds and the application loader.
I have said this many times, sometimes it will work and sometimes it wont.
I first brought this to the notice of the support team on April 1st this year, that is over 4 months ago and people are still reporting errors and M1 seem no closer to resolving it.
This is a pretty important issue because if you cannot upload your apps to iTunes it’s all a bit pointless.

This was posted on Thu Apr 04, 2013
http://www.genuitec.com/support-genuitec/viewtopic.php?f=19&t=5311

@support-octavio wrote:

Hi macauba,

Your problem seems to be the same of stickleback (http://www.genuitec.com/support-genuitec/viewtopic.php?f=8&t=5300), the dev team is already investigating, I’ll follow up with both of you as soon as I get more information.

That was the last I heard!

[robert65]

I am not asking you to delete the project only to do a build with 2.2 and upload to see if it gets by the error, you will know immediately if it solves the issue, then you will at least know if 2.9 is the problem

[FranciscoValenzuela]

It’s definitely a problem with 2.9 cordova, have I done the whole process and tried to send with Cordova 2.9 and does not recognize the certificate, then with the same certificate I have returned to build cordova 2.2 and has been sent successfully.

It is a problem because it is built on 2.9 and widgets will not work, please I need help to fix this as I have spent a very long time in development and is an application with lots of content.

PLEASE HELP….

[robert65]

Glad to hear that your test returned the same result as I logged, at least now the guys at Mobione have a starting point to fix the issue

[support-michael]

robert, franscishift, et al,
We confirmed (what you already know/reported) the itunes connect/application loader rejection for MobiOne 2.5M1 apps built using Cordova 2.5. We have a tracking bug with high priority to address this issue. We will update you as soon as we have movement on it. The plan is to discuss a resolution with the dev team early next Monday.

[robert65]

Wayne, thanks for the update, it’s appreciated, my only concern was that I reported it at least two weeks ago and heard nothing back.

[support-michael]

> I reported it at least two weeks ago and heard nothing back.

Clear. Here’s the scoop: I queued your report for investigation the day you provided the feedback. Also we were triangulating with Kyle at appstoreuploader on the problem. Other than that we did not have anything new to report. I hope you did not think we ignored your feedback.

If you are wondering why we are following up on the Cordova 2.9 today the answer is timing. Due to vacations, limited availability of mac/osx access, milestone-1 status of this mobione issue, itunes acct access restrictions, … we are getting to this issue now. I want to thank Kyle at appstoreuploader whom we partner with for independently investigating this and providing more details. That’s where we are today. This issue is on top of the queue going to next week as some of our key developers return from vacation. I hope this info is helpful.

[robert65]

Wayne, thanks, it was just that when myself and Kyle along with mobione had no answer I knew it could not be anything that I had done different until I traced my steps back to the issues when 2.9 would not upload on the Friday night, so I reverted back an it worked, as I have stated several time my thanks goes to Kyle for the amount of times I must have pestered him trying to get a solution,

[Paul_paul]

I am still using M1 2.3.2 HF which I believe uses Cordova 2.2.
I have had the same error messages on several occasions with this version so I do not think it is exclusive to later versions of Cordova.
I think I first reported this issue before 2.9 was even available. Any thoughts on this?

[robert65]

Stickleback have you tried 2.5m1 to see if that fixes it.

[Paul_paul]

I can’t remember if I did or not, I might try later today, will let you know.

[Muhammad]

I had the same problem also. After read this help forum, finally I found the problem.
2.9 version is problem. I changed to 2.2 and upload is ok now.

But I got three warnings about icons for ipad that could not be loaded. One of the icons is 120×120 size.
Is it new request from Application Loader?

[robert65]

You need to change the app size which currently loads as 114 to the new size if 120 and this will work fine, it’s Apple and iOS7 this time not Mobione, although Mobione needs to change the requested icon size during the build to stop others from not knowing that the app size has changed.

[Author]

Posts