This question is locked. New answers and comments are not allowed.
So, my app builds and runs fine with Cordova 3.0. But, with Cordova 3.2, device.ready never fires (from ios debugger log). This is a fully provisioned app, not icenium. Based on this bug report ...
https://issues.apache.org/jira/browse/CB-5037
I think it has to do with a combination of plugins and Cordova 3.2. It compiles just fine, just no onready. The default config.xml list of plugins does not seem to match the plugins I've checked off in the admin interface in Mist. Help?
https://issues.apache.org/jira/browse/CB-5037
I think it has to do with a combination of plugins and Cordova 3.2. It compiles just fine, just no onready. The default config.xml list of plugins does not seem to match the plugins I've checked off in the admin interface in Mist. Help?
1 Answer, 1 is accepted
0
Hello Ned,
Can you elaborate more about your scenario? What do you mean by "This is a fully provisioned app, not icenium." , are you using Icenium or not? What 3rd party plugins are you using?. Are you using any custom JavaScript framework that might cause this issue? Have you tried to you the device debugging functionality in order to track this issue?
About the plugins in config.xml those are there for Cordova 2.* compatibility. Those are not respected for 3.*, because each plugin (selected from project properties) knows how to add its things to the final config.xml.
Regards,
Stefan Dobrev
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.
Can you elaborate more about your scenario? What do you mean by "This is a fully provisioned app, not icenium." , are you using Icenium or not? What 3rd party plugins are you using?. Are you using any custom JavaScript framework that might cause this issue? Have you tried to you the device debugging functionality in order to track this issue?
About the plugins in config.xml those are there for Cordova 2.* compatibility. Those are not respected for 3.*, because each plugin (selected from project properties) knows how to add its things to the final config.xml.
Regards,
Stefan Dobrev
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.