It appears Pier is absolutely correct and the culprit is in a change Cordova did in v.3.1, namely Unify Whitelist Implemenations
. If you create a brand new Icenium app and do not modify the config.xml, the .apk would be build with the new Cordova implementation, but if you edit the config.xml, we would add an outdated configuration file that still uses the old convention.
In short as Pier listed, for existing apps that have their config.xml file edited, make sure that the following line is changed:
from: <access origin=".*"/>
to: <access origin="*"/>
We would make the necessary changes on our end, so this problem does not surface in subsequent versions.
Sorry for omitting this Cordova change guys (which btw is not listed as breaking)!
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.