[Android] : Preferences Not Available to Plugins

I have been attempting to use the cordova-plugin-code-push alongside tabris-android. Unfortunately the “codepushdeploymentkey” preference along with other preferences are not being parsed/passed to the plugin during initialization. The debug logging statements below demonstrate what is happening:

09-11 05:17:38.153  6517  6517 D logging preferences parsed: {loglevel=DEBUG, codepushdeploymentkey=lhZoVI0z5UWn3GKr6O2_ROTUy-wYVyFgmvTob} 

09-11 05:17:38.450  6517  6517 D logging preferences passed to appView.init: {loglevel=DEBUG, codepushdeploymentkey=lhZoVI0z5UWn3GKr6O2_ROTUy-wYVyFgmvTob}

09-11 05:17:38.450  6517  6517 D logging preferences received in CordovaWebViewImpl.init: {loglevel=DEBUG, codepushdeploymentkey=lhZoVI0z5UWn3GKr6O2_ROTUy-wYVyFgmvTob}

09-11 05:17:39.010  6517  6517 D logging preferences received in to TabrisWebView.init: {}

09-11 05:17:39.010  6517  6517 D logging preferences received in CordovaWebViewImpl.init: {}

My assumption is that the TabrisActivity.java, which I don’t have access to, is not parsing and passing the preferences to plugins that are being initialized. I would appreciate any advice you can give me regarding this, if you are unable to make the preferences available to plugins in a pr.

[cookieguru]

@509dave16 You are absolutely correct; Tabris.js is not a hosting platform. However, assuming you are able to provide the hosting, I believe Tabris.js’ built-in functionality can solve all the other scenarios.

To give an implementation example, you might store a version number inside the app, for example 1.0.1. Upon launch, the app can fetch a remote document to determine the most up-to-date version of the code. If the client has a copy that is older than what that document specifies, then it would call the installPatch method. This would actually be a lot faster than CodePush’s methodolgy of running a diff on every single file in your app. Additionally it provides extra functionality in that you could theoretically patch one of your JavaScript dependencies in node_modules.

For more background on patching in Tabris.js check out this blog post.

[509dave16]

@cookieguru Thanks for the example! I was starting to think along those same lines. I will have to explore Tabris.js patching some more. Appreciate the time you took today to address my issue.