[jira] [Resolved] (CB-2908) DroidGap activity Lifecycle broken issue onDestroy

["Andrew Grieve (JIRA)" <ji...@apache.org>]

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

Andrew Grieve resolved CB-2908.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.0

Thanks Joe! Forgot to update the issue.

Commit: https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=778b784eb6f78a467d010dbfb2ecd2ee0b3ac3fc
                
> DroidGap activity Lifecycle broken issue onDestroy
> --------------------------------------------------
>
>                 Key: CB-2908
>                 URL: https://issues.apache.org/jira/browse/CB-2908
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.7.0
>            Reporter: Andrew Grieve
>            Assignee: Andrew Grieve
>            Priority: Minor
>             Fix For: 2.7.0
>
>         Attachments: snap1.gif, snap2.gif
>
>
> Reported via pull request:
> https://github.com/apache/cordova-android/pull/42
> A DroidGap derived Activity is restarted by the system in an incorrect order due to the finish() invocation onDestroy() upon say, device Config Changes*.
> Upon device Config Changes, onDestroy is followed by a onCreate as promised in:
> http://developer.android.com/reference/android/app/Activity.html#ConfigurationChanges
> Please check attached log snapshots of the issue.
> Attempting to invoke the Activity's finish() onDestroy breaks an Activity's lifecycle flag. OnDestroy can be called by the system, for instance, on restarting an Activity, it's definitely different from a normal finish().
> Finish() incorrectly in onDestroy results in another DroidGap derived activity is started, while the original one is not yet onDestroy. This issue could be found when the system is trying to restart the activity upon, for instance, receiving immediately successive device Config changes.
> The corresponding device "Config Changes" notifications

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira