How do I delete splash screen?

Hi. I build via Cordoba and put this parameter in my manifest. I think it works faster, I only tested it on my test devices.

> "AutoHideSplashScreen" value="true"

Thanks! Will this work exactly the same as removing the line "cordovaInterface.pluginManager.postMessage("setupSplashScreen", splashScreen);" ?

Hi. I build via Cordoba and put this parameter in my manifest. I think it works faster, I only tested it on my test devices.

> "AutoHideSplashScreen" value="true"

and what do you think, is it possible to disable the splash screen in an .aab file?

Construct already automatically hides the splash screen as soon as it is ready to show anything. If you want to hide the splash screen ASAP, the important thing is not to use loader style "none", which shows the splash screen until the entire project is loaded (hiding any loading progress). FWIW the root cause problem here appears to be Google measuring stats incorrectly, so for a real fix, ask Google to fix that.

> Hi. I build via Cordoba and put this parameter in my manifest. I think it works faster, I only tested it on my test devices.

> > "AutoHideSplashScreen" value="true"

and what do you think, is it possible to disable the splash screen in an .aab file?

No. This parameter defaults to "false" in the "config.xml" file. You need to change the value to "true". This should be done before building the package.

Are you sure it's the splash screen, you can attach the apk file. I will look at the logs on a test device. You can also attach a cordova archive as on the screen I will build and check it myself.

Yes, I already did it by deleting the line "cordovaInterface.pluginManager.postMessage("setupSplashScreen", splashScreen)" and the speed of cold start on Google tests increased by 10-12 times...

That's not what I suggested.

You just deleted this line, and you need to activate automatic hiding of the boot screen. There is a fine-tuning of this parameter somewhere, you can specify the time to wait before hiding this screen.

What I suggested above is relevant, I don't know how else to help you.

> Yes, I already did it by deleting the line "cordovaInterface.pluginManager.postMessage("setupSplashScreen", splashScreen)" and the speed of cold start on Google tests increased by 10-12 times...

You just deleted this line, and you need to activate automatic hiding of the boot screen. There is a fine-tuning of this parameter somewhere, you can specify the time to wait before hiding this screen.

Sorry, just to clarify if I understood correctly that I need two actions

1. Delete the line "cordovaInterface.pluginManager.postMessage("setupSplashScreen", splashScreen)"

2. Set true "AutoHideSplashScreen" value="true"

or will only the second action be enough?

Sorry, just to clarify if I understood correctly that I need two actions

1. Delete the line "cordovaInterface.pluginManager.postMessage("setupSplashScreen", splashScreen)"

2. Set true "AutoHideSplashScreen" value="true"

or will only the second action be enough?

No, it's not.

I am building through cordova and before building I need to change one parameter.

You build through android studio, I don't know how to do it there.

> Sorry, just to clarify if I understood correctly that I need two actions

> 1. Delete the line "cordovaInterface.pluginManager.postMessage("setupSplashScreen", splashScreen)"

> 2. Set true "AutoHideSplashScreen" value="true"

>

> or will only the second action be enough?

No, it's not.

I am building through cordova and before building I need to change one parameter.

You build through android studio, I don't know how to do it there.

I did as you said, changing just one parameter on True, it really works a little smoother and faster than deleting the line. Thank you very much!

Via Android Studio everything is exactly the same, in the config.xml file

Why can't you add this to the construct panel?

Because your workaround might be worse. If it is taking several seconds to load the app before Construct is ready to display anything at all, and you disable the splash screen, then the user will open the app and see a blank screen with nothing happening for several seconds. They might think the app is broken, close it, and then uninstall it. The splash screen is vital feedback to say "this app is open and working, wait a moment for it to load".

So long as the loader style is not "none", Construct should be able to hide the splash screen very quickly anyway. All it has to do is load the core HTML and JavaScript file and then it will hide the splash screen and switch to its own loader. I have no idea how that could take more than 1-2 seconds, even on a weak device. So part of the problem here is it's not clear what's actually going on that causes such a long delay on the splash screen.

If you just hack around stuff without dealing with the root cause problem, it often makes things worse, or allows the situation to deteriorate further until it can no longer be worked around, and then you're really stuck. The problem appears to be at least in part that Google are incorrectly measuring splash screen time as the app not responding. This ought to be reported to Google as a bug that they need to fix. The more people who report it the more likely they are to fix it. If they fix it then the situation will be improved and you won't need to do hacks to work around it that might cause users to think your app is not working and uninstall it.

FWIW enabling AutoHideSplashScreen just means "hide the splash screen on a timer". The time delay is SplashScreenDelay, which defaults to 3 seconds on iOS, or when onPageFinished is triggered on Android, according to the documentation. If Construct finishes loading and hides the splash screen before this time, it will have no effect. If you configure this and it hides the splash screen before Construct finishes loading, the user sees the splash screen, then it disappears and they're looking at a blank screen doing nothing again; once again they may think your app is broken, close it and uninstall it.

So I guess you can do that if you want but it doesn't seem like it actually makes the situation better for actual users. Basically you're showing the user a non-responding blank screen to try to work around a measurement bug that affects numbers shown on your dashboard that customers never see. Are you sure you want to do that?

Because your workaround might be worse.

Of course, these 2 seconds might slightly increase the number of users who leave before starting the game session, but what choice do we have? If the ANR rate exceeds 0.47%, Google will remove us from all lists, and organic traffic will drop to zero. What could be worse?