[
https://issues.apache.org/jira/browse/CB-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014693#comment-15014693
]
ASF GitHub Bot commented on CB-8917:
------------------------------------
Github user infil00p commented on the pull request:
https://github.com/apache/cordova-android/pull/239#issuecomment-158229277
@Bnaya @riknoll Unless you're getting a result back from an Activity, the
plugin processes belong to the activity that was put in the background, and the
plugins would die with the activity that was killed. Therefore, there could
only be one result returning to the application. This issue is related to
communication between two activities, not trying to resurrect plugin code,
which is really just class that's not even guaranteed to have its own thread
(although it should).
I think the problems are different enough that the scope shouldn't be
changed here, and that the second problem that your mentioning needs to be
fleshed out more.
> Add api/way to get plugins results even when Cordova activity restarts
> ------------------------------------------------------------------------
>
> Key: CB-8917
> URL: https://issues.apache.org/jira/browse/CB-8917
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android
> Reporter: Bnaya
>
> In android when you have a plugin that opens new activity the CordovaActivity
> will be killed and you won't get the result from the plugin.
> The new activity will get the results but because the plugin objects are dead
> and the webview reloaded you can get the data to the js callback.
> The most noticeable example is the camera plugin. (And maybe its the same
> with even more platforms)
> possible solution for this is to add metadata to the device ready event with
> incoming data from plugins.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]