Github user riknoll commented on the pull request:
https://github.com/apache/cordova-android/pull/239#issuecomment-158224722
@Bnaya That is correct and it was intentional. Is there a need for
extending this to all plugin callbacks currently pending? The way I see it, the
burden is on the app developer for being careful about what plugins are
launching external Activities and maintaining their state accordingly (for
example, not launching the camera activity while waiting on a file transfer).
Plugins have access to the Activity lifecycle on the native side, so they
should be able to handle whatever is happening. I guess plugins lose the
ability to notify the javascript side about what's going on, (like a file
transfer failing) but hopefully the app developer is being careful so that
those situations don't occur.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
