Jump to content
Have similar error. started today, checked just now, still exist. build under MacOS for Android with native extensions, not from simulator
error on start:
Application Validation Error
Incorrect splash screen - the splash screen built into the app is not the one that shipped with build 2018.3257 of Corona
Activate the Corona Splash Screen control plugin
but this plugin is activated for me
It's hard to see what's going on because you're covering up the console log. It's much better to use copy/paste. Select the text in the Console Log window then paste it into a forum post. What I see there doesn't look like an issue with the Splash Screen control. Please copy the content of the log window and share it with us.
21:54:35.774 21:54:35.774 Corona Simulator 2017.3184 (Dec 8 2017 13:24:21) 21:54:35.774 21:54:35.993 21:54:35.993 Copyright (C) 2009-2017 C o r o n a L a b s I n c . 21:54:35.993 Version: 3.0.0 21:54:35.993 Build: 2017.3184 21:54:36.015 Platform: GenericAndroidDevice / x64 / 10.0 / GeForce GT 1030/PCIe/SSE2 / 4.6.0 NVIDIA 391.01 / 2017.3184 / ru_RU | RU | ru_RU | ru 21:54:36.015 Loading project from: M:\Toppler\apk 21:54:36.015 Project sandbox folder: C:\Users\netSk\AppData\Local\Corona Labs\Corona Simulator\Sandbox\apk-ED7725737F07FCC1C9C3200E09FB3716\Documents 21:54:36.030 WARNING: issue found in M:\Toppler\apk\build.settings: 21:54:36.030 WARNING: unrecognized key: settings.iphone.plist.UISupportedInterfaceOrientations~iphone (string) 21:54:36.030 WARNING: unrecognized key: settings.iphone.plist.UISupportedInterfaceOrientations~ipad (string) 21:54:36.030 WARNING: unrecognized key: settings.iphone.plist.UIInterfaceOrientation~iphone (string) 21:54:36.030 WARNING: deprecated key: settings.iphone.plist.CFBundleIconFile (string) 21:54:36.030 WARNING: unrecognized key: settings.iphone.plist.UIInterfaceOrientation~ipad (string) 21:54:40.466 WARNING: Accelerometer events are only available on the device. 21:54:44.651 1920 21:55:04.865 Testing credentials for 'C:\Program Files (x86)\Corona Labs\Corona SDK\Resources\debug.keystore': 21:55:05.923 jar signed. 21:55:05.923 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en 21:55:57.833 BuildID: 5ac654eb31eb5 21:55:58.115 WebServices: downloading build 21:56:02.879 Android build failed (1) after 56 seconds
There isn't anything in the log about splash screen problems. You have an different issue. This thread is about splash screens and when we change subjects, it confuses people looking for info on splash screens or who might have your problem.
In fact there is a thread about your specific problem. Please post your issue here:
and we can continue discussing it.
- What debug steps have you taken?
- When was the last time you successfully built your games/apps.
- What version of Corona were you using before.
- I see you're using 3184. I know that is the public release, but have you tried the latest daily build?
- Have you been able to build any of the demos that come with Corona?
- If, "Yes to last question", have you tried demos that use plugins and built them OK?
- If, "Yes to last two question", have you tried modifying a demo project to add the splash screen plugin and then tried building it? Did that work?
**UPDATE*** Looks like Rob has some better advise for you below.
This sounds like it might be an account issue, but since it worked on OS X...
On PC - You might try:
1. De-authorize 2. Uninstall Corona 3. Reboot (yeah I know this sucks) 4. Re-intsall. 5. Re-authorize.
Windows loses it's mind sometimes and this might help.
Also, be sure you have the right version of JDK installed: https://docs.coronalabs.com/guide/start/installWin/index.html#java-development-kit
Sorry not to have a more exact answer/help.
Have you made any changes to Java in the past few days? If you are not using the splash screen plugin (including it in build.settings), the activation or not has nothing to do with your successful builds. If you can't build sample apps on your PC and you can on a Mac, then it pretty much rules out issues. The error you are seeing is consistent with a Java related issue. Perhaps you've applied a Windows 10 update (or maybe it auto updated) or there was a change in your Java JDK.
This is why I suggested we move this to the other thread. There is plenty of discussion there on things to try (updating your Java to the latest version, converting your existing keystore to a modern format, etc.)
Community Forum Software by IP.Board