Upgrading to the latest Ionic (1.0.1) and Cordova (5.2.0) (npm update -g cordova ionic), starting a new project (and adding Amazon FireOS support), and then attempting to run on a Kindle Fire, I get this fun error message:
[ERROR] Error initializing Cordova: Class not found
Error is shown on startup. Watching the adb log output, the failure seems to be when Cordova is attempting to log the plugins, each failing with things like the following:
D/PluginManager(13205): in getPlugin for service - Device D/PluginManager(13205): exec() call to unknown plugin: Device
Previous versions seemed to work just fine, but for some reason this new release stopped working. A little detective work shows that my platforms/amazon-fireos/res/xml/config.xml isn’t being populated with the plugin references like it used to, missing lines like:
<feature name="Device"> <param name="android-package" value="org.apache.cordova.device.Device" /> </feature>
Android seems to be working just fine with the latest, just not Amazon’s. I do see the plugins listed just fine in the plugins/amazon-fireos.json file, so in theory it should work.
An “ionic platform” run shows that it’s still using Cordova’s v3.6.3 for Amazon, the same as what I’ve used for past Ionic versions (including 1.0.1) without problem, so my guess is that somewhere in the Ionic CLI there was a change that broke Amazon support (and probably similar to Cordova’s issue back in Jan where it assumed all platforms are alphabetical-only, and don’t contain things like dashes in the name).
Anyone else experiencing issues?