[
https://issues.apache.org/jira/browse/CB-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-9620.
----------------------------
Resolution: Won't Fix
I thought I already explained why this was the case in another issue, but I'll
do it again.
Since the plugins are lazy-loaded, onStart and onResume will be ignored unless
you set the plugins to be initialized on startup. When an application starts,
the plugins aren't instantiated until you actually call them. That way,
expensive plugins won't take memory until they are needed. This is a very old
architectural thing, and may not necessarily make sense with the whole plugin
ecosystem we now live, but this is why the plugin lifecycle differs.
> Android plugin lifecycle differs from the standard Android lifecycle
> --------------------------------------------------------------------
>
> Key: CB-9620
> URL: https://issues.apache.org/jira/browse/CB-9620
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 5.1.1
> Reporter: Kai Schlamp
> Priority: Minor
>
> The CordovaPlugin has the same onStart and onResume callback methods as
> Androids Activity class. Unfortunately those differ from the Activity
> Lifecycle (see
> http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle).
> The onStart and onResume methods of CordovaPlugin are not called when the app
> starts for the first time (in contrast to the appropriate Activitiy methods).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
