topic We need to update the UI, the in Software Archive

splash screens problem

amin_a_1 — Mon, 02 Nov 2015 11:33:47 GMT

Hello, I have designed an android app with Construct2, when I want to get an apk file from my app with Intel XDK, I have two problems with Splash Screens: 1. When I import the pics in JPG format, further, I encounter whit build failed message. 2. When I import the pics in PNG format, building the app is successful but on the android device (cellphone), the Splash screen doesn’t display at all !! Please guide me, Thank you.

Did you include the

John_H_Intel2 — Mon, 02 Nov 2015 14:12:24 GMT

Did you include the splashscreen plugin when you built your app?
Did you specify all the splashscreen in the project settings in the XDK?

That is "Splaash" plugin and

amin_a_1 — Tue, 03 Nov 2015 02:19:56 GMT

That is "Splaash" plugin and not relevent to XDK splash screens.

I have specified all the splashscreen with different images and different formats (jpg,png) many times.

Now i am definitely sure that it is some kind of bug in the last version of Intel XDK (2611). I did't have this problem in older versions!

Amin, it sounds like you mean

PaulF_IntelCorp — Tue, 03 Nov 2015 15:22:31 GMT

Amin, it sounds like you mean that these "Splaash" screens are something that is part of the Construct2 game, and not dependent on the Cordova splash screen plugin. If that is the case, you should consult the Construct2 forum. We have no knowledge of how Construct2 apps are constructed, we are only able to help you with XDK-specific issues. The app runs in a Cordova webview on each target, the XDK does not control the behavior of that webview, the platform controls that.

It's not about Construct2 !!!

amin_a_1 — Wed, 04 Nov 2015 04:59:50 GMT

It's not about Construct2 !!!!! when you import a project in intel XDK , there is panel named " Launch icons and splash screens" i have problem whit this zone :

' 1. When I import the pics in JPG format, further, I encounter whit build failed message. "

Save the image as a PNG file

John_H_Intel2 — Wed, 04 Nov 2015 16:15:01 GMT

Save the image as a PNG file (dont just rename it, actually use an image editor to save it as a PNG) and pick that with the XDK.

Yes, with PNG format the

amin_a_1 — Thu, 05 Nov 2015 09:45:55 GMT

Yes, with PNG format the problem will be solved.......but why does the last version of intel xdk (2611) have this problem whit JPG?

Its probably not the XDK, its

John_H_Intel2 — Thu, 05 Nov 2015 16:15:50 GMT

Its probably not the XDK, its more likely a change with Cordova.

It is a problem with Cordova.

PaulF_IntelCorp — Thu, 05 Nov 2015 17:40:00 GMT

It is a problem with Cordova. With the CLI5 release the Cordova project modified the requirements for icons and splash screens so that they MUST be PNG, even though some platforms also support JPG. They did this because it is the lowest-common-denominator across all the platforms. So you'll see that JPG images work with the CLI 4.1.2 builds, but not with the CLI 5.1.1 builds. :(

I think you're right. but, in

amin_a_1 — Fri, 06 Nov 2015 08:22:09 GMT

I think you're right. but, in the "launch icons and splash screens" panel, you can see under each box is this phrase: (JPG/PNG) ,

which means this problem (error with JPG...) is not a programming property , rather it is an unexpectable issue !

and as you know , the Cordova plugin is not an independent app , it's a part whitin the XDK.

We need to update the UI, the

PaulF_IntelCorp — Fri, 06 Nov 2015 17:54:38 GMT

We need to update the UI, the docs have been updated. Unfortunately, the Cordova project did not document this change to the CLI, so we only figured it out after some investigation of similar problems. Cordova is an independent project, it is not owned or directed by Intel or the XDK. We utilize the Cordova project and provide the XDK as a front end to the Cordova CLI.

Ok, now I'm convinced that

amin_a_1 — Sat, 07 Nov 2015 09:13:51 GMT

Ok, now I'm convinced that unsupporting CLI 5 by Cordova is the cause of this problem. Meybe it's better to discuss about this problem at the Cordova support forums.

Anyway, Thank you for your all helpful answers. I hope to see this problem solved in next releases.