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.
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.