Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with splashscreen and cordova-ios 6.0.0 #890

Closed
3 tasks done
mathieucaralp opened this issue Jun 8, 2020 · 5 comments · Fixed by #896
Closed
3 tasks done

Problem with splashscreen and cordova-ios 6.0.0 #890

mathieucaralp opened this issue Jun 8, 2020 · 5 comments · Fixed by #896
Milestone

Comments

@mathieucaralp
Copy link

mathieucaralp commented Jun 8, 2020

Bug Report

Problem

The version 6.0.0 of cordova-ios integrates the splashscreen plugin. Accordingly, the team of cordova-plugin-splashscreen removed the support of this version with the latest version of the plugin.

With that in mind I decided to update cordova-ios to version 6.0.0, but the integrated splashscreen does not work the same way as the plugin one.

What is expected to happen?

The splashscreen should be displayed the same way as before.

What does actually happen?

The splash screen is hidden very quickly, it does not use the settings of the config.xml file. It is hidden even if the AutoHideSplashScreen option is set to false, and the SplashScreenDelay option does not change the delay.

Information

I looked at the CDVViewController.m file file with the Xcode debugger, and it seems that the options of the config.xml file are correctly interpreted, but it does not change nothing.

Moreover when I call the navigator.splashscreen.hide() function, the splashscreen is not displayed and I cannot click on the screen anymore.

Some people from the splashscreen plugin team seem to have spotted the same problem.

Environment, Platform, Device

I use Xcode 11.4 and an IPhone 6S with iOS 13.5.

Version information

I use cordova-ios 6.0.0.

Checklist

  • I searched for existing GitHub issues
  • I updated all Cordova tooling to most recent version
  • I included all the necessary information above
@mosabab
Copy link

mosabab commented Jun 9, 2020

@dpogue Could you please look at this issue:

Cordova-ios does not read the settings from config.xml for splas screen.
This happend since the plugin integrated to cordova-ios.
Regards

@mosabab
Copy link

mosabab commented Jun 9, 2020

@mathieucaralp

Please change the title of this issue to:
cordova-ios 6.0.0 not read the preferences from config.xml for splashscreen

@ajberasategui
Copy link

ajberasategui commented Jun 9, 2020

I'm experiencing the same issue.
What my debugging shows is preferences are correctly read from config.xml. The subview created to "emulate" the Launch Screen after the OSs one is hidden is there but it's transparent. I guess that's the reason why it's not possible to interact with the Web App.

A quick way to prove what I say is to call navigator.splashscreen.show(). Or just set a very long FadeSplashScreenDuration.

I'm still trying to figure out why the launch screen is "transparent" as this is blocking me from upgrading and we really want to.

I also validated that the subview alpha is set to 1.

@dpogue
Copy link
Member

dpogue commented Jun 9, 2020

Ahhhh okay, I know what's happening here: The splashscreen will use the BackgroundColor preference configured in config.xml. If that is not configured, it will be transparent.

I will open a PR in the next few days to make it default to white.

@ajberasategui
Copy link

@dpogue thank you very much for looking at it.
It looks to me like the issue is not only the LaunchScreen storyboard background color. It looks to me like the splash screen image that should be loaded in its image container is not being loaded.
I tried the changes in your PR and what I see in that case is that now the view is visible but it doesn't have the image loaded on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants