[
https://issues.apache.org/jira/browse/CB-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Hayes updated CB-7080:
---------------------------
Description:
There is a long lasting issue related to Android activities being launched a
second time in certain scenarios, this causes issues in Cordova apps (Cordova
events do not get fired).
Bug is reported at Android here:
https://code.google.com/p/android/issues/detail?id=26658
https://code.google.com/p/android/issues/detail?id=2373
Some further discussion in the Phonegap boards here:
https://groups.google.com/forum/#!topic/phonegap/F06WJZl12NI
and a workaround here:
http://stackoverflow.com/questions/4341600/how-to-prevent-multiple-instances-of-an-activity-when-it-is-launched-with-differ/7748416#7748416
Steps to reproduce:
1) Install and launch app via "cordova run" or from the Play Store
2) Tab home button
3) Launch app again
4) Second activity is launched containing activity, no "resume" or
"deviceready" events are fired. As such the app cannot continue to run as we're
waiting on these events to fire first.
This is a long standing issue and whilst it looks like there will be no fix in
Android, it seems it can be fixed using the workaround from the Cordova side of
things. I'm quite astounded that this issue has not been reported before.
There seems to be a loosely related issue here:
https://issues.apache.org/jira/browse/CB-3949
As it stands, on first install from the Play Store, once the user has finished
using the app and decides to go back to it, the app will appear frozen, since
the deviceready event does not fire. The user must kill the app and start it
again but most would not consider doing this before uninstalling the app and
forgetting about it.
was:
There is a long lasting issue related to Android activities being launched a
second time in certain scenarios.
Bug is reported at Android here:
https://code.google.com/p/android/issues/detail?id=26658
https://code.google.com/p/android/issues/detail?id=2373
Some further discussion in the Phonegap boards here:
https://groups.google.com/forum/#!topic/phonegap/F06WJZl12NI
and a workaround here:
http://stackoverflow.com/questions/4341600/how-to-prevent-multiple-instances-of-an-activity-when-it-is-launched-with-differ/7748416#7748416
Steps to reproduce:
1) Install and launch app via "cordova run" or from the Play Store
2) Tab home button
3) Launch app again
4) Second activity is launched containing activity, no "resume" or
"deviceready" events are fired. As such the app cannot continue to run as we're
waiting on these events to fire first.
This is a long standing issue and whilst it looks like there will be no fix in
Android, it seems it can be fixed using the workaround from the Cordova side of
things. I'm quite astounded that this issue has not been reported before.
There seems to be a loosely related issue here:
https://issues.apache.org/jira/browse/CB-3949
As it stands, on first install from the Play Store, once the user has finished
using the app and decides to go back to it, the app will appear frozen, since
the deviceready event does not fire. The user must kill the app and start it
again but most would not consider doing this before uninstalling the app and
forgetting about it.
> App resume broken when app is launched from Play Store or cordova CLI
> ---------------------------------------------------------------------
>
> Key: CB-7080
> URL: https://issues.apache.org/jira/browse/CB-7080
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 3.5.0
> Environment: Android 4.4
> Reporter: Mike Hayes
> Priority: Critical
>
> There is a long lasting issue related to Android activities being launched a
> second time in certain scenarios, this causes issues in Cordova apps (Cordova
> events do not get fired).
> Bug is reported at Android here:
> https://code.google.com/p/android/issues/detail?id=26658
> https://code.google.com/p/android/issues/detail?id=2373
> Some further discussion in the Phonegap boards here:
> https://groups.google.com/forum/#!topic/phonegap/F06WJZl12NI
> and a workaround here:
> http://stackoverflow.com/questions/4341600/how-to-prevent-multiple-instances-of-an-activity-when-it-is-launched-with-differ/7748416#7748416
> Steps to reproduce:
> 1) Install and launch app via "cordova run" or from the Play Store
> 2) Tab home button
> 3) Launch app again
> 4) Second activity is launched containing activity, no "resume" or
> "deviceready" events are fired. As such the app cannot continue to run as
> we're waiting on these events to fire first.
> This is a long standing issue and whilst it looks like there will be no fix
> in Android, it seems it can be fixed using the workaround from the Cordova
> side of things. I'm quite astounded that this issue has not been reported
> before.
> There seems to be a loosely related issue here:
> https://issues.apache.org/jira/browse/CB-3949
> As it stands, on first install from the Play Store, once the user has
> finished using the app and decides to go back to it, the app will appear
> frozen, since the deviceready event does not fire. The user must kill the app
> and start it again but most would not consider doing this before uninstalling
> the app and forgetting about it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
