Recent Updates to Icenium

[Remel]

I am working on an application that was being built against Cordova 3.0 and Kendo UI Mobile v2013.3.1119.  When running on an Android device, using a datasource pointed at a remote JSON endpoint (using a custom transport) works without issue.  

However, as soon as I attempt to build the app against Cordova 3.2 the datasource no longer works and throws error.  I thought that maybe this had something to do with using a version of Kendo UI Mobile that was newer than what is provided by Icenium, but even after switching to that the version the error persisted.  

Switching back to Cordova 3.0 corrects the issue.  Is there some way for me to determine  what the actual error as the only error message returned by jQuery.ajax is "error"?  Have permissions requirements changed in Cordova 3.2 for internet requests?  I currently have the following permissions selected for Android:

ReadPhoneState
Internet
AccessNetworkState

Thanks

[Steve]

Hi Remel,

We're not aware of any changes affecting ajax requests. If you're having problems only when running your app on the Android device, you can setup an http debugging proxy like Fiddler to intercept the device traffic i.e. track the requests/responses - this would help you identify the culprit by giving you a status code or more meaningful error. If you need to debug, a remote debugger would help,  you can check out these posts from our blog for pointers and walkthroughs:

• Remote Debugging Android Devices With jsHybugger
• Remote Debugging Icenium Apps With Weinre

Regards,
Steve
Telerik
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.

[Remel]

Thanks for the links had forgotten about the blog posts about remote debugging, I tried both and wasn't able to get Weinre to work for me.  However, I tried jsHybugger and had unexpected results, with the plugin added I don't experience the problem, ajax requests succeed as expected, however as soon as I remove the plugin and redeploy the app the issue returns.

For now I will just stick with cordova 3.0, since it is working, again thanks for the help.

[Steve]

Hi Remel,

What about FiddlerCap, are the requests passing successfully as well?

Regards,
Steve
Telerik
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.

[Marco]

I had the same problem in my project.    If I  switch from cordova 3.0 to 3.2  the ajax post does not work anymore.
Can you check if the android manifest is built correctly  with the right permission in icenium?

[Steve]

Hi guys,

It appears 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, 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.

Regards,
Steve
Telerik
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.

[Remel]

Thanks for the help Steve, that did the trick.