I am using Corona build 2695 and just testing publishing now.
I selected Build: Beta OSX and I have the correct provisioning certificate selected.
In “After Build” I selected "Send to Mac App Store or create DMG
I get the Building for OS X line and then I see that “send to Mac App store” is greyed out. I hit okay and get this error:
Build Error
Error: validation failed, unable to validate archive
(make sure you are connected to the internet)
What is this error? Internet is fine.
Corona Simulator uses Apple’s Application Loader utility to validate and submit your app to the Mac App Store.
If you get a hard-to-understand error in the Send to Mac App Store part of the build the best thing to do is to run Application Loader by hand and figure out the issue from there (it will either be a problem with Corona’s integration of Application Loader which we can address or an Application Loader issue which you would have to take up with Apple; let us know either way so we can smooth the way for others).
First, build your OS X app in Corona Simulator, choosing Send to Mac App Store and get to the point the error occurs.
Second, you need to run Application Loader which is most easily done by running Xcode and then choosing the menu option:
Xcode > Open Developer Tool > Application Loader
Once Application Loader is running, click on the Choose button in the bottom right corner of the window (there are several ways to open things in Application Loader but this is the only one that will open a package). Navigate to the Save to folder you specified when you built your app and choose the <appname>.pkg file you find there.
Application Loader will do its thing and hopefully the issue will become more apparent. At this point you may need to search for things on the internet to find possible solutions to your dilemma or inform us of a bug that results in apps being built that Application Loader wont work with.
Thanks, I was able to resolve this, thank you for the help!
Hi, I am having this same problem now. The last time I used the “Send to App Store” feature during a build, it worked fine - that was a few weeks ago. Today, it doesn’t work. No change in provisioning certificates. No change to anything.
I receive the message, “Build Error” and “ERROR” validation failed: Unable to validate archive. (make sure you are connected to the internet)"
When I try and upload my AppName.ipa directly with Application Loader, I now receive new errors that I didn’t get before:
The u option must have a non-emptry value.
The password must have a non-empty value.
(not new) The resulting API analysis file is too large. We are unable to validate your API usage prior to delivery. This is just an informational message.
I am running Corona version 2721. Any help is much appreciated.
Can you update to either 2731, the latest public build or a later daily build?
Thanks
Rob
After installing today’s Daily Build 2747, the Build Error in Corona remained.
However, by installing the latest of Apple’s Application Loader 3.1, I was able to upload the .ipa file generated by Corona to iTunes Connect without any trouble.
If you are using our built in uploader and are having problems, can you run this command from the terminal:
defaults write com.coronalabs.Corona_Simulator debugBuildProcess 3
Then send us the whole log file (CMD-A, CMD-C from the terminal window, CMD-V in the forum post reply).
If you’re not using our built in uploader, then this is an Apple problem since we just run whatever the default Application Loader is on your computer and we don’t pass any parameters and such.
Rob
Sure, I’ll check that later but it should be worth noting that the IPA created by Corona with the latest build can be uploaded to iTunesConnect with Application Loader 3.1; that Application Loader 3.2 does not work with the Corona-generated IPA file.
Does it work with other IPA files?
I can confirm the behaviour troylyndon describes.
I am able to upload manually with Application Loader 3.1 but validation fails with AL 3.2.
I get this error in AL 3.2: The password must have a non-empty value.
Corona Simulator uses Apple’s Application Loader utility to validate and submit your app to the Mac App Store.
If you get a hard-to-understand error in the Send to Mac App Store part of the build the best thing to do is to run Application Loader by hand and figure out the issue from there (it will either be a problem with Corona’s integration of Application Loader which we can address or an Application Loader issue which you would have to take up with Apple; let us know either way so we can smooth the way for others).
First, build your OS X app in Corona Simulator, choosing Send to Mac App Store and get to the point the error occurs.
Second, you need to run Application Loader which is most easily done by running Xcode and then choosing the menu option:
Xcode > Open Developer Tool > Application Loader
Once Application Loader is running, click on the Choose button in the bottom right corner of the window (there are several ways to open things in Application Loader but this is the only one that will open a package). Navigate to the Save to folder you specified when you built your app and choose the <appname>.pkg file you find there.
Application Loader will do its thing and hopefully the issue will become more apparent. At this point you may need to search for things on the internet to find possible solutions to your dilemma or inform us of a bug that results in apps being built that Application Loader wont work with.
Thanks, I was able to resolve this, thank you for the help!
Using the latest build: 2779 I’m getting an error when selecting “Create DMG” and build.
In the console it says:
ERROR: Build Error: ERROR: plugin code signing for ‘/Users/myname/Desktop/MyApp.app/Contents/Plugins/plugin_fuse.lu’ failed: /Users/myname/Desktop/MyApp.app/Contents/Plugins/plugin_fuse.lu: replacing existing signature
/Users/MyName/Desktop/MyApp.app/Contents/Plugins/plugin_fuse.lu: timestamps differ by 235 seconds - check your system clock
I’m not sure what this has to do with Sending to the Mac App Store …
I’ve haven’t seen that particular error before except when I’ve changed the time on my computer to test something.
Is your computer time synchronized with the internet? “Set date and time automatically” should be checked in the Date & Time System Preferences (this is an Apple codesigning requirement, not something to do with Corona).
Because it’s related to sending to the Mac App store - I’m creating the package to send to iTunes connect, I would have started a new thread, but didn’t want to clutter up the forum. I also tested send to Mac App Store which didn’t work, and threw an error, but I usually don’t select that option anyway.
I went ahead and used build 2702 and it didn’t give me the fuse error, and was able to submit successfully, so something with the newest daily build is causing the error with Mac App builds, and shouldn’t be asking for the Fuse plugin since I don’t have it in my project folder, nor is the checkbox available to check fuse.
And to answer your question, yes that box is checked for date/time, never had issues with that before,
You said you were ‘getting an error when selecting “Create DMG”’ which isn’t what you’d do to send an app to iTunes Connect (you need to create a package file).
In any case, I’m a bit confused about what you’re trying to do. The Fuse plugin isn’t available for OS X so I’m unclear how you got things to the point of the signing failure you’re seeing. Even if you went to the trouble of editing the build.settings to add the stub that wouldn’t cause the error you are seeing. That error tells you exactly what to do: check your system clock
Apologies, apparently we add the plugin_fuse.lu file to the build. But that doesn’t cause the error you are seeing, that error tells you exactly what to do: check your system clock
I made an error above, meant to say I was getting this error creating the .pkg file
Why did the check system clock only appear in this build, and not 2702 which I’ve been able to successfully submit apps? Are you absolutely sure fuse wasn’t the culprit with the system clock error too?
I checked the system clock again, and it is exactly as it should be, tested building and it seems to have worked now.
Hi, I am having this same problem now. The last time I used the “Send to App Store” feature during a build, it worked fine - that was a few weeks ago. Today, it doesn’t work. No change in provisioning certificates. No change to anything.
I receive the message, “Build Error” and “ERROR” validation failed: Unable to validate archive. (make sure you are connected to the internet)"
When I try and upload my AppName.ipa directly with Application Loader, I now receive new errors that I didn’t get before:
The u option must have a non-emptry value.
The password must have a non-empty value.
(not new) The resulting API analysis file is too large. We are unable to validate your API usage prior to delivery. This is just an informational message.
I am running Corona version 2721. Any help is much appreciated.
Can you update to either 2731, the latest public build or a later daily build?
Thanks
Rob
After installing today’s Daily Build 2747, the Build Error in Corona remained.
However, by installing the latest of Apple’s Application Loader 3.1, I was able to upload the .ipa file generated by Corona to iTunes Connect without any trouble.