Hi all,
I could not upload my app because I miss the metadata.xml file in the zip file produced after building in Corona. Can somebody explain me what I need to do?
Also, if I open Application Loader, it cannot select the zip file.
Thx,
Farid
We are also receiving this error now. This happens after pressing the button to submit to Apple when building with our distribution profile. We are building for iOS SDK 6.1 with Corona v2013.1202 and have Xcode v5.0 with Application Loader v2.9. We have never experienced this issue before and have submitted builds as recently as 3-4 weeks ago (note that was before updating to Corona 1202 and Xcode 5.0). We need to submit a new build immediately so any information on this would be greatly appreciated.
Actual Error:
Metadata Not Found
There was a problem opening the package <file path>/<gamename>.zip
Unable to find metadata.xml at location: <file path>/<gamename>.zip
I’m having the same exact problem here. I need to upload an update immediately. Also, is it safe to build with 7.0 beta?
Thanks.
Xcode 5.0 does indeed present the message however, it only does this if you launch the Application Loader from Corona using the “Upload to App Store…” button that presents itself at the end of the device build if (and only if) you use a Store cert. Pressing this seems to trigger the issue. Just use Application Loader directly from Xcode for now while we figure out what the problem is. Also, from my observation, it appears you can just ignore this error message anyway.
I uploaded a test binary via the “Deliver Your App” option in Xcode 5.0, and was able to submit a binary and did NOT see any subsequent messaging related to missing metadata.
You cannot build for distribution using a beta SDK (to comply with Apple rules) so stick with 6.1 for now. There’s no functional difference between the two as far as Corona apps are concerned.
I had this same problem but discovered that I had simply forgotten to go to the app’s iTunes Connect page and hit “Ready to Upload Binary”. Once I activated that, it went through without a hitch.
But if you have not hit “Ready to Upload Binary”, you wouldn’t be able to select the application from the Application Loader drop down.
Same problem corona sdk 1228 osx 10.8.5
Same problem here, too. (I did click “Ready to Upload Binary”)
Should I use XCode or igonre the error? It seems there is no specific answer for this problem yet?
We successfully uploaded our last build a while ago by just ignoring the error and opening Application Loader right through Xcode (Xcode -> Open Developer Tool -> Application Loader). The package that was created during the build process was able to be submitted without a problem. It has since been approved and live for a while now without any known issues.
Note: It is still a little nerve racking though anytime you are submitting a package that has previously told you that there was an error with a missing file.
We are also receiving this error now. This happens after pressing the button to submit to Apple when building with our distribution profile. We are building for iOS SDK 6.1 with Corona v2013.1202 and have Xcode v5.0 with Application Loader v2.9. We have never experienced this issue before and have submitted builds as recently as 3-4 weeks ago (note that was before updating to Corona 1202 and Xcode 5.0). We need to submit a new build immediately so any information on this would be greatly appreciated.
Actual Error:
Metadata Not Found
There was a problem opening the package <file path>/<gamename>.zip
Unable to find metadata.xml at location: <file path>/<gamename>.zip
I’m having the same exact problem here. I need to upload an update immediately. Also, is it safe to build with 7.0 beta?
Thanks.
Xcode 5.0 does indeed present the message however, it only does this if you launch the Application Loader from Corona using the “Upload to App Store…” button that presents itself at the end of the device build if (and only if) you use a Store cert. Pressing this seems to trigger the issue. Just use Application Loader directly from Xcode for now while we figure out what the problem is. Also, from my observation, it appears you can just ignore this error message anyway.
I uploaded a test binary via the “Deliver Your App” option in Xcode 5.0, and was able to submit a binary and did NOT see any subsequent messaging related to missing metadata.
You cannot build for distribution using a beta SDK (to comply with Apple rules) so stick with 6.1 for now. There’s no functional difference between the two as far as Corona apps are concerned.
I had this same problem but discovered that I had simply forgotten to go to the app’s iTunes Connect page and hit “Ready to Upload Binary”. Once I activated that, it went through without a hitch.
I got the first error also. when I tried to go through the Application Loader, I got: ITMS-9000 invalid routing app setting
Just run Application Loader directly. Click on the Spotlight magnifying class at the top right, type in Application Loader and then click on the one that says “Application” and it will launch it for you. Then you can send your app without this error. We are looking into fixing it, but this is the work-around for now.
I got that error inside the Application Loader directly several times, in fact. my clients are freaking out!
The full message: ERROR ITMS-9000: “In valid routing app setting: To upload a routing app coverage file on iTunes Connect, you must define the app binary as a routing app.” as SoftwareAssets/AoftwareAsset(MZItmspSoftareAsset Package)
says it’s unable to Authenticate the package…
it turned out to be the geojson file I was forced to upload (it was supposed to be optional, but it wouldn’t let me move on until I uploaded one). I went back and deleted it and the app went up in a flash!!!
Not all app submission issues are the same thing.
The issue that started this forum thread is with the “Upload to App Store” button in the Simulator causing an error concerning “metadata.xml” when you’ve installed Xcode 5.0. The interim solution is to not use that button in the Simulator but use Xcode directly.
Other App Store submission issues are almost certainly unrelated. As we all know, you have to get your certs and provisioning lined up just so or Apple will throw an error. If you get an error you haven’t seen before, you’ll have to go to search the web and try to find someone who has already figured it out or post a new thread here asking if anyone has seen the issue before.
my original discovery of this issue came from research when I tried to use the alternative method of publishing out of Corona when the App Uploader didn’t work. I couldn’t find any info on the issue I was having with the app uploader so I posted my dilemma here hoping to find someone who had encountered a similar problem because this project needed to be published right away. when I discovered the solution I shared it here as well. there may be others who have encountered this error, who were forced to upload geojson files as I was who will now know the solution. all of my other ducks were certainly in the proverbial row…I didn’t know I was violating any forum rules by publishing my query here, and I’m sorry if I did. Desperate times, etc…