incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Ehrlich (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-139) Prompts generated on remote webpages
Date Sat, 14 Jan 2012 02:54:40 GMT


Peter Ehrlich commented on CB-139:

sure, I'll give it a test.

I tried building with ant, but got an error:

$ ant
Buildfile: /Users/peter/Rails/incubator-cordova-android/framework/build.xml

/Users/peter/Rails/incubator-cordova-android/framework/build.xml:14: Source
resource does not exist:

Total time: 0 seconds

Is it easy to send instructions? I figure its something I should be able to

I forked the repo -- I'll try some comments and things for fun.


On Fri, Jan 13, 2012 at 8:38 PM, Anis Kadri (Commented) (JIRA) <

> Prompts generated on remote webpages
> ------------------------------------
>                 Key: CB-139
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 1.2.0
>            Reporter: Alex Mayfield
>            Assignee: Anis Kadri
> The majority of an application that I am developing is located on a remote website (and
is loaded from the first page with a window.location.href). For the most part, it works fine,
however I have discovered that the hardware "Back" button on Android does not function as
expected (it backs out of the entire application) and thus have tried to override it with
a back button callback.
> However, I have found that my attempt to include phonegap.js on the remote website is
having some unexpected consequences. As soon as I get to the remote page, I am getting spammed
with prompt after prompt that contains things such as the following:
> gap:["Device","getDeviceInfo","Device0",true]
> Looking at phonegap.js, it appears that this is coming from line 628, which is in the
function that handles communication with the native side of phonegap.
> Any ideas?

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


View raw message