[ 
https://issues.apache.org/jira/browse/CB-13628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

jcesarmobile closed CB-13628.
-----------------------------
    Resolution: Won't Fix

As far as I know this only happens when the apps are installed from Xcode, so 
it shouldn't happen on production apps.

Anyway, the one that caches the image is the device, there is nothing we can do 
about it, it also happens in native apps. So closing as won't fix.

The only workaround is to use a different image name.

> Cached iOS LaunchStoryboard image displayed before updated LaunchStoryboard 
> image. 
> -----------------------------------------------------------------------------------
>
>                 Key: CB-13628
>                 URL: https://issues.apache.org/jira/browse/CB-13628
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-plugin-splashscreen
>    Affects Versions: cordova-ios 4.5.0
>         Environment: iOS
>            Reporter: Ivy Nye
>            Priority: Minor
>
> If an old launch storyboard image is cached on the device, it is displayed on 
> launch and then fades to the current LaunchStoryboard image. 
> *Steps:*
> 1. Deploy to iOS with LaunchStoryboard set to image1.
> 2. Change LaunchStoryboard to image2 and redeploy.
> 3. See image1, followed by a quick fade to image2.
> _Resetting the device will clear this cache, but we cannot expect this from 
> users._
> I have found that removing the LaunchStoryboard Image View form 
> CDVLaunchScreen.storyboard will prevent this image from being cached, and it 
> will still display after the initial view transition. 
> Also, a background color can be set on the initial view which will not be 
> cached. It may be useful to be able to set the backgroundColor of the 
> storyboard via config.xml.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to