Critical Showstopper - Cannot upload Corona build app to the app store

Solar2D General Questions/Discussion
#21

Here’s the Info.plist and the embedded provision certificate, I even tried running codesign to see the same. I am at my wits end.

@Rob, The certificate *IS* a distribution certificate, this is not the first time that I am uploading an app to the app store.

I can attach a screenshot that shows that the Distribtution Certificate is chosen when the build is chosen.

On completion of the build, the corona build process runs validation and I get an all OK. In fact I even thought that Corona uses the wrong certificate while compiling/building so using codesign and other utilities I have had a look and the certificate is a proper distribution certificate and NOT an Ad Hoc or Developer.

I am just short of buying a new mac so that I can compile with Corona and update this application since I have cleaned up all the mobile provision certificates, re-created just this certificate and still the same.

Is this something to do with the fact that my subscription *used* to be PRO but since it has not been renewed, Corona is doing something that prevents the build?

Please tell me what logs/screenshots you need to resolve this, I can provide them to you, I need to get this resolved.

I will try that last bit of a dummy .app but if that works, what could the issue really be???

#22

@007

Have you checked your keychain on your Mac (using Keychain Access) to verify that you don’t have any duplicate or invalid certificates?

(BTW, Info.plist is perfectly fine. Xcode 5.1.1 is being used)

#23

@007

Yet another question.

How do you get your certificates into Xcode? 

Do you do it manually (download, etc, etc), or do you let Xcode do the work for you?

#24

@Ingemar,

 Download it from the Portal using SAFARI and then double clicking it which starts xCode and installs it in the MobileProvisions directory. Then shut down Corona entirely and restart it to get the updated list which includes the Distribution profile.

#25

Have you tried letting Xcode do the work for you instead?

I’m not sure, but it *might* just clean things up. I can explain how if your haven’t tried it before.

#26

@ingemar, thanks for that, but I had downloaded all the certificates via xcode initially.

I made a standard application in xCode and let xCode make an archive and then validate and upload it using the certificate that is installed. It worked without a hitch and quite fast.

I ran another application to check the .app,

The difference between the .app created by Corona and xCode was the object Code format is

Corona -> “bundle with generic”

xCode -> “bundle with Mach-O universal (armv7 armv7s (16777228:0))”

The remaining stuff like the certificates, code signature, etc are the same.

Now I can’t simple replace the .app in the .xcarchive

So the outcome of this exercise was that the Certificate is ok and not an issue as the focus has been, the issue is that the .zip created by Corona is not liked by Application Loader for some reason and that has started with the new version of xCode.

If Corona can modify the settings for the xcode project from the back end on the server, I believe there is something that needs to be done there at the backend servers.

If it helps this app is not Universal and is build only for a single iOS device and in the build.settings the CFBundle entries are uncommented to make them specific than to avoid the com.bundle.IDENTIFIER type dynamic setting.

Any suggestions now?

#27

I have an app that needs to be updated soon so I created a new version and uploaded a dummy app to test the uploading procedure.

I compiled it with 2189a (Public version), and I also added your specific CFBundlexxxxx settings to my build.settings. It uploaded fine:

and the binary details look like this in iTunes Connect after being uploaded:

I’m at a loss to why your setup doesn’t work.

#28

@007

What happens if you remove CFBundleIdentifier from build.settings and resubmit?

It’s not really necessary as it will pick the identifier from the distribution profile you sign it with (unless the distribution profile has a wildcard in it)

#29

@ingemar, it is the same with and without the CFBundle settings, it fails.

The device family is not Universal in my case, it is available only for the iPhones.

I appreciate you putting in time to help me resolve this.

#30

I dug a little deeper to see what Application Loader does… it keeps creating this .itmsp file which is the package that it uploads to App Store created in the /var/folders/ path. the generated metadata.xml file has a software_assets key now could the error be pertaining to this?

Corona used to generate a metadata.xml document so maybe you can help here…

But the bottom line remains that it is unable to upload, really frustrating…

#31

@007

Is sure is weird since you can upload a dummy app from Xcode using the same certificate. 

To make matters even more strange, I can upload an app compiled with Corona 2189a as seen above.

#32

@007 

Just a thought: Do you have any AdHoc certificates for this app?

If so, maybe Xcode is choosing that instead of the App Store Distribution profile…

#33

As you can see there is just one profile, I deleted the rest of the profiles. So there isn’t any other AdHoc or other certificate left there to have chosen incorrectly.

#34

That is what puzzles me most, that the certificate is right as it is accepted when a dummy app is uploaded.

Just a thought, you are an enterprise customer and current, where as my account was a PRO and no longer valid so could there be something there? If it was not critical for the client to get the updates to the new version I would have not bothered.

#35

Let’s see if we can sort this out…

This is the dummy Corona app I made to upload to Apple. I was able to upload it without any issues.

Try compiling this with Corona 2189a without modifications, using your distribution certificate.

Let’s see if Apple will accept it or not when you try to upload it…

#36

@007, the screen shot of your build settings really doesn’t help show the issue.  Look at my build settings profiles:

ProvProfile2.png

Notice I have 4 “Distribution” profiles.  However only one of them is for the store.  I specifically name mine with the phrase “Distribution” or “AdHoc” when I create them.  Both will show as “Distribution” on that screen.

Rob

#37

@Rob

The strange thing is that he can build an Xcode dummy app, sign it with his certificate and Apple accepts it.

However, his Corona compiled app isn’t accepted when using the same certificate.

#38

I just built an app with 2189a, using a known Distribution (for the store) and it uploaded just fine.

This points to an Xcode or profile problem. 

Rob

#39

I know… I’ve been able to compile and upload with 2189a too.

That’s what’s weird with his setup since he can compile and upload a native Xcode project with his profile…

#40

I don’t know if Xcode is using the profiles in ~/Library/MobileDevice/Provioning Profiles or not.  It’s possible that a rogue profile is there.  Perhaps it’s worth it to delete everything out of there and re-download them.  I generally don’t use Xcode to manage these.  I download them by hand and move them to that folder.

Rob