cordova plugin framework tag

[Fab_V_]

hi,

I'm using Badge plugin : https://github.com/katzer/cordova-plugin-badge

the latest update, enables the badge icon on android app but the build failed.
After some investigations i found the problem, due to framework tag in plugin.xml that does not seem to be parsed during the build.
Any other users are experiencing an identical problem ?

Is there any solution ?

Cordova 4.1.2 build - Android.

THX

[Fab_V_]

the author's reply says :

I have corrected the engine requirements. You need to update plugman.
the plugin.xml addition :
...engine name="cordova-plugman" version=">=4.2.0" ...< !-- needed for gradleReference support -- >

question  : how to update plugman in intel xdk ??
 

[PaulF_IntelCorp]

You are not able to update plugman, it is part of the build system. His version reference indicates that his plugin needs at least Cordova CLI version 4.2.0, not the 4.1.2 that we currently have in our build system. Our system is getting an upgrade in the near future to CLI 5.x. When that happens the plugin you are trying to use should work with our build system.

In the meantime, you might continue to use an older version of that plugin or build locally using CLI. If you are going to build locally, I recommend you switch to the EA version of the XDK, since it will work more co-operatively with a local copy of CLI. See these docs: https://software.intel.com/en-us/xdk/docs/lp-early-access

[Monish_O_]

It's over 2 months. When's the update?!

[Anusha_M_Intel1]

Our system is getting an upgrade in the near future to CLI 5.x. When that happens the plugin you are trying to use should work with our build system.

This happened in the v2496 release. Are you still not able to use the badge plugin? Do try it again in the latest 2548 release. 

[Hieu_N_]

This still not resolved yet with Intel XDK 2087. Can anyone help? Thanks.

[PaulF_IntelCorp]

The way the debug module is being built is being changed to be compatible with the new CLI 5 build system, but is not yet live. That should fix the issue. I'm not sure how long it will be until that new debug module build system is available.

In the meantime, you have two options for debugging:

• debug the built app using remote CDT (see https://software.intel.com/en-us/xdk/docs/intel-xdk-debug-and-test-overview#RemoteChromeDevTools)
• create a debug module that does not include that problem plugin and debug everything but that part of your code with that slimmed down debug module (temporarily remove the problem plugin from your project and use the Debug tab to build the debug module, when you add the plugin back to your project, do NOT update the debug module, just continue to use the slimmed down one)

If you take the second approach, you'll have to put some guards around the code the calls the problem plugin APIs and either fake it out or just skip that code.