You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Nikhil Khandelwal (JIRA)" <ji...@apache.org> on 2016/02/01 20:34:39 UTC

[jira] [Resolved] (CB-8342) SplashScreen plugin doesn't destroy it's views which seems to block user interaction

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

Nikhil Khandelwal resolved CB-8342.
-----------------------------------
    Resolution: Incomplete

Please provide more details and repro instructions

> SplashScreen plugin doesn't destroy it's views which seems to block user interaction
> ------------------------------------------------------------------------------------
>
>                 Key: CB-8342
>                 URL: https://issues.apache.org/jira/browse/CB-8342
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin SplashScreen
>            Reporter: Jamal Johnson
>              Labels: ios, splashscreen, triaged, wfc
>
> We recently updated the SplashScreen plugin for iPhone 6/6+ support but uncovered an issue that appears to have been caused by a fix for another issue.
> There was a bug report (https://issues.apache.org/jira/browse/CB-7204) concerning it sounds like a race condition with the spinner and the splash screen and the fix was to make sure the animation "completed" by checking a boolean passed to the animation "completion" function, when hiding the SplashScreen, before destroying it's views. This boolean, according to the docs, will be false if another view is animated in before this one was "completed".
> Here is the commit with the fix: d2e62a551c950041cb4c9683624a04d931f4bee3 (https://github.com/apache/cordova-plugin-splashscreen/commit/d2e62a551c950041cb4c9683624a04d931f4bee3)
> We have a case where we have another view (a PinLock plugin) that sometimes gets animated in before the SplashScreen animation is fully complete. There doesn't seem to be any issues with this and is transparent to the user. However, with the addition of checking the "finished" boolean before destroying the views, the app becomes unusable. If we comment that conditional out, everything works fine again.
> Is there another way to handle fixing the race condition? Or any other suggestions?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org