Android splash-screen-duration deprecated with 3.1.0 -- use SplashScreenDelay

  • 1
  • Announcement
  • Updated 5 years ago
To define how long your android splash displays as of 3.1.0, use the following in your config.xml file:

<preference name="SplashScreenDelay" value="5000" />

Cordova 3.1.0 Android sees the addition of the SplashScreenDelay preference, which replaces PhoneGap Build's android-specific splash-screen-duration preference.
Photo of ryan

ryan, Developer

  • 1538 Posts
  • 132 Reply Likes

Posted 7 years ago

  • 1
Photo of Oren Agiv

Oren Agiv

  • 84 Posts
  • 3 Reply Likes
In order to set the Splash to immediately disappear - are these two preferences correct for PhoneGAP Build 3.1 config.xml:


<!-- iOS: Auto hides the splash on iOS -->
<preference name="AutoHideSplashScreen" value="true" />

<!-- android: Timeout for the Splash on Android in milliseconds -->
<preference name="SplashScreenDelay" value="0" />
Photo of Juan Carlos Alpizar Chinchilla

Juan Carlos Alpizar Chinchilla

  • 38 Posts
  • 1 Reply Like
Should this be implemented in the documentation of phonegap buld 3.1.0 as well? it took me a couple hours to find this out cause this wasn't in the documentation, found a stack overflow article and when I came to report it I found this in the support forum... documentation would be a more accurate place to put this kind of information.
Photo of ryan

ryan, Developer

  • 1538 Posts
  • 132 Reply Likes
Thanks for the feedback Juan -- you're right that we're not clearly linking to the PhoneGap / Cordova documentation. Thanks for the heads up, will fix that.
Photo of Ab Lopez

Ab Lopez

  • 70 Posts
  • 9 Reply Likes
And this is isn't fixed as of today... the PGB documentation is very poor and confusing. You previously had a complete list of all the available options we could use in the config.xml file and now the page at http://docs.build.phonegap.com/en_US/... is skimpy and doesn't mention all the possibilities, one has to guess and do Google searches to find what to use for different cases. BTW, I'm a PAID customer for over a year.
Photo of ismael jimoh

ismael jimoh

  • 4116 Posts
  • 192 Reply Likes
Hi,

Your issue is unrelated as I see your issue relates to iPad and the question if you read relates to Android.

In the mean time, you can find most of what should work here(view links for each platforms also. I am not assuring you they will all work, reason for short queue is those are the ones guaranteed to work).

Thanks.
Photo of Ab Lopez

Ab Lopez

  • 70 Posts
  • 9 Reply Likes
My issue with the splash screen plugin on iPad has nothing to do with this particular topic. I'm commenting on this issue as this setting isn't having any effect in both iPhone and iPad.

And the documentation is still poor, leaving much to be desired for a paid service.

First, the documentation at http://docs.build.phonegap.com/en_US/... doesn't link to http://docs.phonegap.com/en/3.5.0/con....

Then, the documentation you suggest at http://docs.phonegap.com/en/3.5.0/con... doesn't list all the possibilities for the config.xml in the Build Service. It's as poor as the other.

To be completely frank, you waste developers' time when things are documented so poorly and one has to depend on Google, Stackoverlow and the community support forum to get information that should be OPENLY and CLEARLY available in a SINGLE place: the PhoneGap Build documentation.
Photo of Raymond Camden

Raymond Camden

  • 29 Posts
  • 0 Reply Likes
Are the docs seriously not updated for this? It looks like it was raised 11 months ago and I ran into the same problem today.
Photo of Petra V.

Petra V., Champion

  • 7794 Posts
  • 1391 Reply Likes
The current documentation on "preferences" is, indeed, poorly maintained.
This thread's issue is still mentioned in the docs as:
splash-screen-duration (android only)
Duration that the splash screen remains visible; defaults to 5000 (ms). For auto-hide behaviour call navigator.splashscreen.hide() in the deviceready callback.
Example:
<preference name="splash-screen-duration" value="10000"/>

The brand new SplashScreenDelay as of PGB3.1.0 (we're at 3.7.0 now) still isn't included.
http://docs.build.phonegap.com/en_US/...
Photo of Ab Lopez

Ab Lopez

  • 70 Posts
  • 9 Reply Likes
Do you know who's in charge of maintaining documentation at PGB? Answer: Nobody (at least it seems like it).

Seems PGB is only worried about keeping the service operational and keeping up with new PhoneGap versions and adding occasional improvements.

They should really add a full-time person or two for maintaining documentation and providing daily support on these community forums.

If they cannot afford it, at least they should put the documentation as a wiki in Github so we can all maintain it as a community.
Photo of Petra V.

Petra V., Champion

  • 7794 Posts
  • 1391 Reply Likes
I only agree partly with your perception:
1. The PGB team (with tech lead Brett) is responsible for the docs. Not "Nobody".
2. The team is understaffed since Ismael and Zahir left the team last Summer. However, Adobe took the sub pages for jobs offline: http://phonegap.com/blog/2014/06/20/p... (see links for job description on that page)
3. It's Adobe hiring! Adobe is big enough to afford necessary staff. But can they find excellent applicants? Have you applied for a job?
4. The folks asking questions on this board are at fault, too. Questions about CSS trouble, jQuery, web services and the procedure for creating iOS certificates, for instance, are off topic here and unnecessarily consume staff time.

That said, yes, the documentation is poorly maintained. And yes, relevant questions are sometimes answered/handled much too late (issues appear to fall off the radar spontaneously....).
What may users expect from a free (or almost free) service?
Photo of Ab Lopez

Ab Lopez

  • 70 Posts
  • 9 Reply Likes
I understand your defensive stand, but keep in mind this:

1. What's the use of being responsible of something when the evidence clearly indicates otherwise?
2. They have been in that condition for months. You'll find quite a few local native iOS/Android dev shops in your city that will have very talented and experienced devs, and they don't had such a hard time to recruit and retain their staff, or to replace someone when they leave.
3. I'm not looking for a job, I'm looking for a professional service from PGB, which is being paid. You can be a big-enough company yet not be able to recruit talent and keep it, which is what worries me as a paid customer since PGB's beginnings.
4. Definitely, I concur with that. That's why in the past I've requested the PGB team through this forum to create a separate paid plan that includes ticket-based support, or at least a private forum, where only questions related to the service (and not to HTML/CSS, PhoneGap basics, etc.) can be posted, and then answered by PGB so that other customers can have this knowledge base at their disposal.

This doesn't have to be a free service forever. And I'm not demanding such a level of service for a free product. But when you're a paid customer since the very beginnings, I think you're in all your right to demand a professional level of service, in all aspects.

As devs, that's what our clients expect and require from us, why shouldn't we expect that from our providers?
Photo of ryan

ryan, Developer

  • 1538 Posts
  • 132 Reply Likes
Summary of Android Splash delay preferece:

splash-screen-duration
This is a PhoneGap Build custom preference that we implemented before the Cordova project added SplashScreenDelay and we've left it for (a) backwards-compatibility, and (b) we'd seen no reason to remove it (though now I see it is causing confusion and will remove it).

SplashScreenDelay
This is a PhoneGap preference (not managed by PGB). We don't keep a copy of the list of Cordova's supported preference on the PGB Docs, we simply link to them.

The above distinction is explained at the top of the PGB Preferences doc:

All preference tags in your config.xml are copied to the platform-specific configuration files, which means that any preferences supported by the PhoneGap framework, or by any plugins you are using, will work on PhoneGap Build.
...
In addition, PhoneGap Build supports some of its own custom preferences, used for things like selecting the PhoneGap version, platform sdk version targeting, and others. These custom preferences are listed below.


On Build we don't copy all of the preferences from the PhoneGap docs to the Build docs, since these change every time a PhoneGap version is released.

We know our docs have been neglected and are out of date. We're doing what we can with our resources -- including lobbying for resources dedicated to this. Hopefully this will improve.
Photo of Petra V.

Petra V., Champion

  • 7794 Posts
  • 1391 Reply Likes
We know our docs have been neglected and are out of date. We're doing what we can with our resources -- including lobbying for resources dedicated to this. Hopefully this will improve.
I sense a bit of frustration, here. Understandably so!
Thanks for your explanation, Ryan.