cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Grieve (JIRA)" <>
Subject [jira] [Commented] (CB-1525) PG 2.1: onDeviceReady() is not being called remotely, only locally
Date Mon, 15 Oct 2012 14:52:07 GMT


Andrew Grieve commented on CB-1525:

Maybe just wait for 2.2 to be released. We should have an RC out either today or tomorrow
that you can try.
> PG 2.1: onDeviceReady() is not being called remotely, only locally 
> -------------------------------------------------------------------
>                 Key: CB-1525
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.1.0
>         Environment: iPad 2, iOS 6, PhoneGap 2.1, Xcode 4.5
>            Reporter: Julio Cezar
>            Assignee: Andrew Grieve
>              Labels: onBodyLoad, onDeviceReady
>             Fix For: 2.2.0
> After upgrading to PhoneGap 2.1, my onDeviceReady() method is not being called anymore,
on the server side. I have a HTML file locally, and locally the method onDeviceReady is being
called without any problems. But after being redirected to a web page application, the onDeviceReady()
method is not being called anymore. I did not have this kind of issue using PhoneGap 2.0.
I have the same problem with the method onBodyLoad(): its being called without problems locally,
but not on the server side, remotely.
> I have made a completely new (template) Project, using the console (PG "create" script),
and added the www folder to my server. Locally (local index.html), the native App makes a
redirection to the index.html in the remote www folder. I have realized, that the same problem
always happen: the onDeviceLoad method is not being called. And that's the template project
from phonegap. Locally it works ok, but not when its on the server. The allowed ExternalHosts
has been set to '*' (all hosts allowed).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message