[jira] [Updated] (CB-4691) Fix Xcode 5 warnings
[ https://issues.apache.org/jira/browse/CB-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-4691: - Attachment: warnings.png > Fix Xcode 5 warnings > > > Key: CB-4691 > URL: https://issues.apache.org/jira/browse/CB-4691 > Project: Apache Cordova > Issue Type: Task > Components: iOS >Affects Versions: 3.0.0 > Environment: Xcode 5 DP6 >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah >Priority: Minor > Labels: ios7 > Fix For: 3.1.0 > > Attachments: warnings.png > > > See screenshot as well. > CDVViewController.m:657:41: Undeclared selector > 'shouldOverrideLoadWithRequest:navigationType:' > CDVViewController.m:658:45: Undeclared selector > 'shouldOverrideLoadWithRequest:navigationType:' -- 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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4690) WP8 Call https in CordovaView.xaml.cs
[ https://issues.apache.org/jira/browse/CB-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctrlz Apps updated CB-4690: --- Priority: Critical (was: Major) > WP8 Call https in CordovaView.xaml.cs > - > > Key: CB-4690 > URL: https://issues.apache.org/jira/browse/CB-4690 > Project: Apache Cordova > Issue Type: Bug > Components: WP7, WP8 >Affects Versions: 2.4.0 >Reporter: Ctrlz Apps >Assignee: Jesse MacFadyen >Priority: Critical > > When I try to call a https address from CordovaView.xaml.cs, I receive an > undefined error and the method CordovaBrowser_NavigationFailed is executed. > Https address has a FNMT Clase 2 Certificate installed -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752186#comment-13752186
]
Armno Prom commented on CB-4404:
It seems to be a bug of Android's WebView with fullscreen activities. Please
see https://code.google.com/p/android/issues/detail?id=5497
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>Priority: Minor
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4692) Native GeoLocation support is not fully working
Wolfgang Koller created CB-4692: --- Summary: Native GeoLocation support is not fully working Key: CB-4692 URL: https://issues.apache.org/jira/browse/CB-4692 Project: Apache Cordova Issue Type: Bug Components: Plugin Geolocation, WP7, WP8 Affects Versions: 3.0.0 Reporter: Wolfgang Koller Assignee: Steve Gill The current Geolocation implementation of Cordova is using the native, built in, support of Internet Explorer. However the native code does not support Altitude, AltitudeAccuracy and heading properties (they are always null). Therefor it is required to add our own implementation based on GeoCoordinateWatcher. -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4692) Native GeoLocation support is not fully working
[ https://issues.apache.org/jira/browse/CB-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752194#comment-13752194 ] Wolfgang Koller commented on CB-4692: - I'm already working on this and my code is in beta stage. It can be found here: https://github.com/Viras-/cordova-plugin-geolocation/ Once I'm done I will push this to the apache repos. You might want to assign this Issue to me (I can't change the Assignee for whatever reason). > Native GeoLocation support is not fully working > --- > > Key: CB-4692 > URL: https://issues.apache.org/jira/browse/CB-4692 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Geolocation, WP7, WP8 >Affects Versions: 3.0.0 >Reporter: Wolfgang Koller >Assignee: Steve Gill > > The current Geolocation implementation of Cordova is using the native, built > in, support of Internet Explorer. > However the native code does not support Altitude, AltitudeAccuracy and > heading properties (they are always null). > Therefor it is required to add our own implementation based on > GeoCoordinateWatcher. -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4681) jQuery Ajax callbacks not executed
[
https://issues.apache.org/jira/browse/CB-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752257#comment-13752257
]
Jonathan Naguin commented on CB-4681:
-
I have this working. I had to add this lines at the end of _changeReadyState_
method on _XHRHelper.cs_:
{code}
if (this.readyState == XHRShim.DONE){
this.onload && this.onload();
}
{code}
It seems that onload is not fired automatically...
> jQuery Ajax callbacks not executed
> --
>
> Key: CB-4681
> URL: https://issues.apache.org/jira/browse/CB-4681
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP8
>Affects Versions: 3.0.0
> Environment: Windows 8 Professional
>Reporter: Jonathan Naguin
>Assignee: Jesse MacFadyen
>Priority: Critical
>
> I have an Ajax request to a server, but the _success_ callback or any
> callback is not executed even if the server respond with a 200 code (I saw
> the logs using Wireshark).
> {code}
> $.ajax({
> url: 'http://example.com',
> data: { foo: 'bar' },
> dataType: 'json',
> success: function (data) {
> console.log(data);
> },
> error: function(){
> console.log("Error");
> },
> complete: function(){
> console.log("Complete");
> }
> });
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4693) Typo in camera.mediatype example
John M. Wargo created CB-4693: - Summary: Typo in camera.mediatype example Key: CB-4693 URL: https://issues.apache.org/jira/browse/CB-4693 Project: Apache Cordova Issue Type: Improvement Components: Docs Affects Versions: 3.0.0 Reporter: John M. Wargo Assignee: Michael Brooks Priority: Minor In the mediatype example, the ending curly brace is outside of the code area. http://cordova.apache.org/docs/en/3.0.0/cordova_camera_camera.md.html#cameraOptions -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4686) env: node\r: No such file or directory on all Cordova commands on new install of 3.0.7
[ https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752356#comment-13752356 ] Jānis commented on CB-4686: --- The same on Ubuntu 13.04 > env: node\r: No such file or directory on all Cordova commands on new install > of 3.0.7 > -- > > Key: CB-4686 > URL: https://issues.apache.org/jira/browse/CB-4686 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX 10.7.5 >Reporter: Ross James >Assignee: Filip Maj >Priority: Blocker > > All Cordova commands in Mac OSX terminal are now returning: > env: node\r: No such file or directory -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4686) env: node\r: No such file or directory on all Cordova commands on new install of 3.0.7
[ https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752377#comment-13752377 ] Ian Clelland commented on CB-4686: -- A couple of questions to help track this down: - What commands are you running? - How did you install cordova? - Can you paste any more error output, or is that all? - Does the '\r' appear literally in your terminal output? > env: node\r: No such file or directory on all Cordova commands on new install > of 3.0.7 > -- > > Key: CB-4686 > URL: https://issues.apache.org/jira/browse/CB-4686 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX 10.7.5 >Reporter: Ross James >Assignee: Filip Maj >Priority: Blocker > > All Cordova commands in Mac OSX terminal are now returning: > env: node\r: No such file or directory -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4686) env: node\r: No such file or directory on all Cordova commands on new install of 3.0.7
[ https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752390#comment-13752390 ] Jānis commented on CB-4686: --- h6. On Ubuntu 13.04: Updated cordova through terminal with "npm update cordova -g". It updated to cordova 3.0.7 from 3.0.6. Then launching cli command "cordova" only outputs ": No such file or directory" on a new line, so the '\r' does not appear to me. It isn't the terminal itself outputting the line, meaning the cordova file is found in the bin. > env: node\r: No such file or directory on all Cordova commands on new install > of 3.0.7 > -- > > Key: CB-4686 > URL: https://issues.apache.org/jira/browse/CB-4686 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX 10.7.5 >Reporter: Ross James >Assignee: Filip Maj >Priority: Blocker > > All Cordova commands in Mac OSX terminal are now returning: > env: node\r: No such file or directory -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4686) env: node\r: No such file or directory on all Cordova commands on new install of 3.0.7
[ https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752421#comment-13752421 ] Ian Clelland commented on CB-4686: -- It looks like that is a symptom of Windows line endings (CRLF) being present in the node script files. If I run unix2dos on the scripts, then I get the same error message. Bash is confused by the "\r" before the "\n" Unix newline. I installed cordova freshly from npm (into a temp dir) and I can see the bad line endings on the bin/cordova file. Possibly the latest release was packaged and published from a Windows machine, and broke everything. > env: node\r: No such file or directory on all Cordova commands on new install > of 3.0.7 > -- > > Key: CB-4686 > URL: https://issues.apache.org/jira/browse/CB-4686 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX 10.7.5 >Reporter: Ross James >Assignee: Filip Maj >Priority: Blocker > > All Cordova commands in Mac OSX terminal are now returning: > env: node\r: No such file or directory -- 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: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4694) CLI commands no longer work when going from 3.0.6 to 3.0.7
Steve Husting created CB-4694: - Summary: CLI commands no longer work when going from 3.0.6 to 3.0.7 Key: CB-4694 URL: https://issues.apache.org/jira/browse/CB-4694 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Environment: Max OSX Reporter: Steve Husting Assignee: Filip Maj *Every one* of my Cordova commands in Mac OSX terminal are now returning: env: node\r: No such file or directory ... after upgrading to 3.0.7. They worked fine before. I used the following to upgrade: sudo npm update -g cordova I tried the command again and problem remains. -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4694) CLI commands no longer work when going from 3.0.6 to 3.0.7
[ https://issues.apache.org/jira/browse/CB-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752475#comment-13752475 ] Luc Franken commented on CB-4694: - Same issue appears here on Mac OSX: 10.8.4: Steps to follow to reproduce: $ mkdir hello $ cordova create hello com.example.hello HelloWorld env: node\r: No such file or directory $ cordova env: node\r: No such file or directory NPM version $ npm -v 1.3.8 CORDOVA package version $ npm list -g /usr/local/lib ├─┬ cordova@3.0.7 > CLI commands no longer work when going from 3.0.6 to 3.0.7 > -- > > Key: CB-4694 > URL: https://issues.apache.org/jira/browse/CB-4694 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Max OSX >Reporter: Steve Husting >Assignee: Filip Maj > > *Every one* of my Cordova commands in Mac OSX terminal are now returning: > > env: node\r: No such file or directory > > ... after upgrading to 3.0.7. They worked fine before. I used the following > to upgrade: > sudo npm update -g cordova > I tried the command again and problem remains. -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4694) CLI commands no longer work when going from 3.0.6 to 3.0.7
[ https://issues.apache.org/jira/browse/CB-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752473#comment-13752473 ] RDO commented on CB-4694: - Same here, windows-style line endings in several files broke the module. > CLI commands no longer work when going from 3.0.6 to 3.0.7 > -- > > Key: CB-4694 > URL: https://issues.apache.org/jira/browse/CB-4694 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Max OSX >Reporter: Steve Husting >Assignee: Filip Maj > > *Every one* of my Cordova commands in Mac OSX terminal are now returning: > > env: node\r: No such file or directory > > ... after upgrading to 3.0.7. They worked fine before. I used the following > to upgrade: > sudo npm update -g cordova > I tried the command again and problem remains. -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4564) [BlackBerry10] Prevent rogue files from being added to frameworkModules.js
[ https://issues.apache.org/jira/browse/CB-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752520#comment-13752520 ] ASF subversion and git services commented on CB-4564: - Commit e9fa1f05a1c3d36b207a9c74a84a75d6f6b899b6 in branch refs/heads/master from [~daudino] [ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=e9fa1f0 ] [CB-4564]Only alow .js files into frameworkModules Reviewed By: Bryan Higgins Tested By: Tracy Li > [BlackBerry10] Prevent rogue files from being added to frameworkModules.js > -- > > Key: CB-4564 > URL: https://issues.apache.org/jira/browse/CB-4564 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.0.0 >Reporter: Bryan Higgins >Assignee: Bryan Higgins > Fix For: 3.1.0 > > > Its possible to get hidden files (for instance .DSStore or .swp or Mac) added > into the frameworkModules file. We should check that only JavaScript is going > in. -- 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: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4695) Messaging API plugin
Shazron Abdullah created CB-4695:
Summary: Messaging API plugin
Key: CB-4695
URL: https://issues.apache.org/jira/browse/CB-4695
Project: Apache Cordova
Issue Type: Wish
Components: Android, iOS
Affects Versions: Master
Reporter: Shazron Abdullah
Assignee: Joe Bowser
Priority: Minor
This was sent to me from a Cordova user:
{quote}
One of my suggestions for the future would be that an SMS plugin be included as
part of the core API as it just seems anti-intuitive that a mobile framework
cannot allow a developer to access one of the most widely used functionalities
of mobile phones out-of-the-box.
It was a genuine shock to me that something like Compass is included as part of
the core API which has an extremely small use case whereas the biggest use case
of sending SMSs is not covered and is only available third party.
{quote}
We do have the SysApps spec:
http://messaging.sysapps.org/
--
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: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-4695) Messaging API plugin
[
https://issues.apache.org/jira/browse/CB-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah reassigned CB-4695:
Assignee: (was: Joe Bowser)
> Messaging API plugin
>
>
> Key: CB-4695
> URL: https://issues.apache.org/jira/browse/CB-4695
> Project: Apache Cordova
> Issue Type: Wish
> Components: Android, iOS
>Affects Versions: Master
>Reporter: Shazron Abdullah
>Priority: Minor
>
> This was sent to me from a Cordova user:
> {quote}
> One of my suggestions for the future would be that an SMS plugin be included
> as part of the core API as it just seems anti-intuitive that a mobile
> framework cannot allow a developer to access one of the most widely used
> functionalities of mobile phones out-of-the-box.
> It was a genuine shock to me that something like Compass is included as part
> of the core API which has an extremely small use case whereas the biggest use
> case of sending SMSs is not covered and is only available third party.
> {quote}
> We do have the SysApps spec:
> http://messaging.sysapps.org/
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752601#comment-13752601
]
Joe Bowser commented on CB-4404:
I can't reproduce this on Android 4.3 on the HTC One. Trying with the Samsung
Galaxy S4 with TouchWiz.
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>Priority: Minor
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752608#comment-13752608
]
Joe Bowser commented on CB-4404:
OK, Yes, this is fullscreen related. Unfortunately, this is browser-related.
That being said, there MIGHT be a way to polyfil a fix.
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>Priority: Minor
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4586) Exception when trying to call close() on In-App Browser instance
[
https://issues.apache.org/jira/browse/CB-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Gill updated CB-4586:
---
Component/s: Android
Assignee: (was: Steve Gill)
> Exception when trying to call close() on In-App Browser instance
>
>
> Key: CB-4586
> URL: https://issues.apache.org/jira/browse/CB-4586
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin InAppBrowser
>Affects Versions: 3.0.0
> Environment: Tested on Android 4.3 / Nexus 4 and Nexus 10
>Reporter: Victor Costan
>
> Code sketch:
> {code:javascript}
> var browser = window.open(oauthUrl, '_blank', 'location=yes');
> browser.addEventListener('loadstop', function() {
> if (/* event.url matches the OAuth response URL*/ true) {
> browser.close();
> }
> });
> {code}
> Stack trace from adb logcat.
> {code}
> W/webview_proxy(27421): java.lang.Throwable: Warning: A WebView method was
> called on thread 'WebViewCoreThread'. All WebView methods must be called on
> the UI thread. Future versions of WebView may not support use on other
> threads.
> W/webview_proxy(27421): at
> android.webkit.WebView.checkThread(WebView.java:1918)
> W/webview_proxy(27421): at
> android.webkit.WebView.loadUrl(WebView.java:771)
> W/webview_proxy(27421): at
> org.apache.cordova.core.InAppBrowser.closeDialog(InAppBrowser.java:316)
> W/webview_proxy(27421): at
> org.apache.cordova.core.InAppBrowser.execute(InAppBrowser.java:161)
> W/webview_proxy(27421): at
> org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:65)
> W/webview_proxy(27421): at
> org.apache.cordova.PluginManager.execHelper(PluginManager.java:229)
> W/webview_proxy(27421): at
> org.apache.cordova.PluginManager.exec(PluginManager.java:214)
> W/webview_proxy(27421): at
> org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
> W/webview_proxy(27421): at
> android.os.Handler.dispatchMessage(Handler.java:99)
> W/webview_proxy(27421): at android.os.Looper.loop(Looper.java:137)
> W/webview_proxy(27421): at
> android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:814)
> W/webview_proxy(27421): at java.lang.Thread.run(Thread.java:841)
> W/System.err(27421): java.lang.RuntimeException: java.lang.Throwable:
> Warning: A WebView method was called on thread 'WebViewCoreThread'. All
> WebView methods must be called on the UI thread. Future versions of WebView
> may not support use on other threads.
> W/System.err(27421): at android.webkit.WebView.checkThread(WebView.java:1927)
> W/System.err(27421): at android.webkit.WebView.loadUrl(WebView.java:771)
> W/System.err(27421): at
> org.apache.cordova.core.InAppBrowser.closeDialog(InAppBrowser.java:316)
> W/System.err(27421): at
> org.apache.cordova.core.InAppBrowser.execute(InAppBrowser.java:161)
> W/System.err(27421): at
> org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:65)
> W/System.err(27421): at
> org.apache.cordova.PluginManager.execHelper(PluginManager.java:229)
> W/System.err(27421): at
> org.apache.cordova.PluginManager.exec(PluginManager.java:214)
> W/System.err(27421): at
> org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
> W/System.err(27421): at android.os.Handler.dispatchMessage(Handler.java:99)
> W/System.err(27421): at android.os.Looper.loop(Looper.java:137)
> W/System.err(27421): at
> android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:814)
> W/System.err(27421): at java.lang.Thread.run(Thread.java:841)
> W/System.err(27421): Caused by: java.lang.Throwable: Warning: A WebView
> method was called on thread 'WebViewCoreThread'. All WebView methods must be
> called on the UI thread. Future versions of WebView may not support use on
> other threads.
> W/System.err(27421): at android.webkit.WebView.checkThread(WebView.java:1918)
> W/System.err(27421): ... 15 more
> D/dalvikvm(27421): GC_CONCURRENT freed 410K, 5% free 937
[jira] [Updated] (CB-4586) Exception when trying to call close() on In-App Browser instance
[
https://issues.apache.org/jira/browse/CB-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-4586:
---
Priority: Minor (was: Major)
> Exception when trying to call close() on In-App Browser instance
>
>
> Key: CB-4586
> URL: https://issues.apache.org/jira/browse/CB-4586
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin InAppBrowser
>Affects Versions: 3.0.0
> Environment: Tested on Android 4.3 / Nexus 4 and Nexus 10
>Reporter: Victor Costan
>Priority: Minor
>
> Code sketch:
> {code:javascript}
> var browser = window.open(oauthUrl, '_blank', 'location=yes');
> browser.addEventListener('loadstop', function() {
> if (/* event.url matches the OAuth response URL*/ true) {
> browser.close();
> }
> });
> {code}
> Stack trace from adb logcat.
> {code}
> W/webview_proxy(27421): java.lang.Throwable: Warning: A WebView method was
> called on thread 'WebViewCoreThread'. All WebView methods must be called on
> the UI thread. Future versions of WebView may not support use on other
> threads.
> W/webview_proxy(27421): at
> android.webkit.WebView.checkThread(WebView.java:1918)
> W/webview_proxy(27421): at
> android.webkit.WebView.loadUrl(WebView.java:771)
> W/webview_proxy(27421): at
> org.apache.cordova.core.InAppBrowser.closeDialog(InAppBrowser.java:316)
> W/webview_proxy(27421): at
> org.apache.cordova.core.InAppBrowser.execute(InAppBrowser.java:161)
> W/webview_proxy(27421): at
> org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:65)
> W/webview_proxy(27421): at
> org.apache.cordova.PluginManager.execHelper(PluginManager.java:229)
> W/webview_proxy(27421): at
> org.apache.cordova.PluginManager.exec(PluginManager.java:214)
> W/webview_proxy(27421): at
> org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
> W/webview_proxy(27421): at
> android.os.Handler.dispatchMessage(Handler.java:99)
> W/webview_proxy(27421): at android.os.Looper.loop(Looper.java:137)
> W/webview_proxy(27421): at
> android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:814)
> W/webview_proxy(27421): at java.lang.Thread.run(Thread.java:841)
> W/System.err(27421): java.lang.RuntimeException: java.lang.Throwable:
> Warning: A WebView method was called on thread 'WebViewCoreThread'. All
> WebView methods must be called on the UI thread. Future versions of WebView
> may not support use on other threads.
> W/System.err(27421): at android.webkit.WebView.checkThread(WebView.java:1927)
> W/System.err(27421): at android.webkit.WebView.loadUrl(WebView.java:771)
> W/System.err(27421): at
> org.apache.cordova.core.InAppBrowser.closeDialog(InAppBrowser.java:316)
> W/System.err(27421): at
> org.apache.cordova.core.InAppBrowser.execute(InAppBrowser.java:161)
> W/System.err(27421): at
> org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:65)
> W/System.err(27421): at
> org.apache.cordova.PluginManager.execHelper(PluginManager.java:229)
> W/System.err(27421): at
> org.apache.cordova.PluginManager.exec(PluginManager.java:214)
> W/System.err(27421): at
> org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
> W/System.err(27421): at android.os.Handler.dispatchMessage(Handler.java:99)
> W/System.err(27421): at android.os.Looper.loop(Looper.java:137)
> W/System.err(27421): at
> android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:814)
> W/System.err(27421): at java.lang.Thread.run(Thread.java:841)
> W/System.err(27421): Caused by: java.lang.Throwable: Warning: A WebView
> method was called on thread 'WebViewCoreThread'. All WebView methods must be
> called on the UI thread. Future versions of WebView may not support use on
> other threads.
> W/System.err(27421): at android.webkit.WebView.checkThread(WebView.java:1918)
> W/System.err(27421): ... 15 more
> D/dalvikvm(27421): GC_CONCURRENT freed 410K, 5% free 9371
[jira] [Reopened] (CB-3576) Add support for self-signed SSL certficates in InAppBrowser
[
https://issues.apache.org/jira/browse/CB-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve reopened CB-3576:
---
Assignee: Andrew Grieve (was: Joe Bowser)
Re-opening - I think the summary of the discussion is that this is something
that should be added, but via an interstitial rather than a programmatic API.
> Add support for self-signed SSL certficates in InAppBrowser
> ---
>
> Key: CB-3576
> URL: https://issues.apache.org/jira/browse/CB-3576
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android, iOS, Plugin InAppBrowser
>Affects Versions: 2.7.0, 2.8.0
> Environment: Android and iOS
>Reporter: Montyleena
>Assignee: Andrew Grieve
> Labels: android, https, inappbrowser,, ios, ssl
> Attachments: InAppBrowser.java
>
>
> Local https links are blocked by default in InAppBrowser (links using a local
> SSL certificate which can't be verified by a 3rd party). Ideally, user should
> be given an option to proceed or cancel the request like the default
> desktop/mobile browsers do.
> Right now, we have to overwrite the following API in Android to access such
> URLs but onReceivedSslError() function gets called only for the main PhoneGap
> window browser and not for InAppBrowser.
> Create a new class:
> public class CustomWebViewClient extends CordovaWebViewClient {
>
> public static final String LOG_TAG = "Plugin";
>
> public CustomWebViewClient(DroidGap ctx) {
> super(ctx);
> Log.d(LOG_TAG, "Constructor!");
> }
> @Override
> public void onReceivedSslError(WebView view, SslErrorHandler handler,
> SslError error) {
> handler.proceed();
> }
> }
> In the main class, we use our custom class as a web view client
> CordovaWebViewClient webViewClient = new CustomWebViewClient(this);
> webViewClient.setWebView(this.appView);
> this.appView.setWebViewClient(webViewClient);
> And similar type of code needs to be written for iOS.
> InAppBrowser should pick up the SSL settings from the main web view and once
> we overwrite the onReceivedSslError() function, then it should allow such
> URLs in the InAppBrowser too.
--
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-4404:
---
Priority: Major (was: Minor)
Increasing the priority before I close this as won't fix, because this is
irritating as all crap. The calls that I would use to override this have been
deprecated, so I can't rely on them to be future-proof. I wish Android WebView
wasn't such a pile of crap.
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752703#comment-13752703
]
Joe Bowser edited comment on CB-4404 at 8/28/13 6:39 PM:
-
I can't really resolve bugs with the Android WebView, which this is. I think
you could implement a plugin to fix this, but it would require that the text
field detect that it has focus, then send it to native, and force the WebView
to scroll. I think this should be done as an optional plugin, because so many
things could go terribly wrong with this.
was (Author: bowserj):
I think this is a better resolution. I can't resolve bugs with the Android
WebView, which this is. I think you could implement a plugin to fix this, but
it would require that the text field detect that it has focus, then send it to
native, and force the WebView to scroll. I think this should be done as an
optional plugin, because so many things could go terribly wrong with this.
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752703#comment-13752703
]
Joe Bowser commented on CB-4404:
I think this is a better resolution. I can't resolve bugs with the Android
WebView, which this is. I think you could implement a plugin to fix this, but
it would require that the text field detect that it has focus, then send it to
native, and force the WebView to scroll. I think this should be done as an
optional plugin, because so many things could go terribly wrong with this.
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4696) Can't build iOS CDVNotification.m in Dialog Plug-in
David Peacock created CB-4696: - Summary: Can't build iOS CDVNotification.m in Dialog Plug-in Key: CB-4696 URL: https://issues.apache.org/jira/browse/CB-4696 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugin Dialogs Affects Versions: 3.0.0 Environment: MacOS XCode 4.5 Reporter: David Peacock Assignee: Shazron Abdullah Create a cordova project, add the dialog plug-in and try to build (XCode/Cordova build). The build fails with an error in CDVNotification.m. The issue is in playBeep() where it calls soundCompletionCallback. The error is "Use of undeclared identifier 'soundCompletionCallback'". Both soundCompletionCallback and playBeep are static methods which call each other. They need to be declared explicitly first. -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3949) Add code fix to broken activity sequence
[
https://issues.apache.org/jira/browse/CB-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752856#comment-13752856
]
Jason Farnsworth commented on CB-3949:
--
This fix breaks the official PushPlugin for sending push notifications.
Clicking on a notification opens a push-handling Activity, which then hands off
to the main activity. However, this fix shuts the main activity down before it
can start.
Overall this fix seems dangerous. It's checking for a special case on an intent
and then just shutting it down?
Can this please be reverted.
> Add code fix to broken activity sequence
>
>
> Key: CB-3949
> URL: https://issues.apache.org/jira/browse/CB-3949
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0, 2.8.0
>Reporter: Kuan Yi Ming
>Assignee: Joe Bowser
>Priority: Minor
> Attachments: Cordova281-debug.apk
>
>
> If installing an app via sideloading on Android and opening it immediately
> after install via package installer, going through several pages, then
> pressing Home and later resuming the app later via opening the app from the
> may break the page sequence by creating a new CordovaActivity instance on top
> of the previous one.
> Tested on a Galaxy Nexus, Android 4.2
> Steps to replicate:
> # Copy attached APK over to phone storage and install it.
> # Click 'Open' when the package installer has installed the app, instead of
> clicking 'Done'
> # Press the button in index.html to open the next page.
> # Press Home to pause the app, then reopen the app from the app drawer (not
> the Recent Apps list).
> # The app will relaunch as if it were a new activity instance (showing
> splashscreen again if configured, and adds index.html to the page sequence,
> instead of returning to where the user last was)
> # Pressing back at this index page closes the new CordovaActivity and returns
> to the second page from the previous activity.
> These steps can't be replicated if the app was originally opened in the app
> drawer, a shortcut in the homescreen, or launched via Eclipse's Run button.
> Some bugs filed on Android's issue tracker suggest this can happen by
> clicking 'Open' on apps freshly installed from the Play Store too.
> This probably is an Android issue with the package installer (probably due to
> the package installer calling a non-standard intent) and not PhoneGap, but
> appears to be fixed by using singleTop as the activity launch mode, or adding
> code before calling super.loadUrl() in the activity to check for Intent
> anomalies:
> {code:java}
> Intent intent = getIntent();
> String intentAction = intent.getAction();
> if (!isTaskRoot() && intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
> intentAction != null) {
> if(intentAction.equals(Intent.ACTION_MAIN)) {
> Log.d("Cordova", "This isn't the root activity. Clearing it
> and returning to the root activity.");
> finish();
> return;
> }
> }
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-3949) Add code fix to broken activity sequence
[
https://issues.apache.org/jira/browse/CB-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752856#comment-13752856
]
Jason Farnsworth edited comment on CB-3949 at 8/28/13 9:17 PM:
---
This fix breaks the official PushPlugin for sending push notifications.
Clicking on a notification opens a push-handling Activity, which then hands off
to the main activity. However, this fix shuts the main activity down before it
can start.
Overall this fix seems dangerous. It's checking for a special case on an intent
and then just shutting it down?
Can this please be reverted.
See: https://github.com/phonegap-build/PushPlugin/issues/35
was (Author: jdhiro):
This fix breaks the official PushPlugin for sending push notifications.
Clicking on a notification opens a push-handling Activity, which then hands off
to the main activity. However, this fix shuts the main activity down before it
can start.
Overall this fix seems dangerous. It's checking for a special case on an intent
and then just shutting it down?
Can this please be reverted.
> Add code fix to broken activity sequence
>
>
> Key: CB-3949
> URL: https://issues.apache.org/jira/browse/CB-3949
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0, 2.8.0
>Reporter: Kuan Yi Ming
>Assignee: Joe Bowser
>Priority: Minor
> Attachments: Cordova281-debug.apk
>
>
> If installing an app via sideloading on Android and opening it immediately
> after install via package installer, going through several pages, then
> pressing Home and later resuming the app later via opening the app from the
> may break the page sequence by creating a new CordovaActivity instance on top
> of the previous one.
> Tested on a Galaxy Nexus, Android 4.2
> Steps to replicate:
> # Copy attached APK over to phone storage and install it.
> # Click 'Open' when the package installer has installed the app, instead of
> clicking 'Done'
> # Press the button in index.html to open the next page.
> # Press Home to pause the app, then reopen the app from the app drawer (not
> the Recent Apps list).
> # The app will relaunch as if it were a new activity instance (showing
> splashscreen again if configured, and adds index.html to the page sequence,
> instead of returning to where the user last was)
> # Pressing back at this index page closes the new CordovaActivity and returns
> to the second page from the previous activity.
> These steps can't be replicated if the app was originally opened in the app
> drawer, a shortcut in the homescreen, or launched via Eclipse's Run button.
> Some bugs filed on Android's issue tracker suggest this can happen by
> clicking 'Open' on apps freshly installed from the Play Store too.
> This probably is an Android issue with the package installer (probably due to
> the package installer calling a non-standard intent) and not PhoneGap, but
> appears to be fixed by using singleTop as the activity launch mode, or adding
> code before calling super.loadUrl() in the activity to check for Intent
> anomalies:
> {code:java}
> Intent intent = getIntent();
> String intentAction = intent.getAction();
> if (!isTaskRoot() && intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
> intentAction != null) {
> if(intentAction.equals(Intent.ACTION_MAIN)) {
> Log.d("Cordova", "This isn't the root activity. Clearing it
> and returning to the root activity.");
> finish();
> return;
> }
> }
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4586) Exception when trying to call close() on In-App Browser instance
[
https://issues.apache.org/jira/browse/CB-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752861#comment-13752861
]
ASF subversion and git services commented on CB-4586:
-
Commit 8b52796a8959aa96ed986ef520e1f94df3650715 in branch refs/heads/master
from [~bowserj]
[
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-inappbrowser.git;h=8b52796
]
CB-4586: Making loadUrl run on the UI thread for close dialog to stop the
WebView error
> Exception when trying to call close() on In-App Browser instance
>
>
> Key: CB-4586
> URL: https://issues.apache.org/jira/browse/CB-4586
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin InAppBrowser
>Affects Versions: 3.0.0
> Environment: Tested on Android 4.3 / Nexus 4 and Nexus 10
>Reporter: Victor Costan
>Priority: Minor
>
> Code sketch:
> {code:javascript}
> var browser = window.open(oauthUrl, '_blank', 'location=yes');
> browser.addEventListener('loadstop', function() {
> if (/* event.url matches the OAuth response URL*/ true) {
> browser.close();
> }
> });
> {code}
> Stack trace from adb logcat.
> {code}
> W/webview_proxy(27421): java.lang.Throwable: Warning: A WebView method was
> called on thread 'WebViewCoreThread'. All WebView methods must be called on
> the UI thread. Future versions of WebView may not support use on other
> threads.
> W/webview_proxy(27421): at
> android.webkit.WebView.checkThread(WebView.java:1918)
> W/webview_proxy(27421): at
> android.webkit.WebView.loadUrl(WebView.java:771)
> W/webview_proxy(27421): at
> org.apache.cordova.core.InAppBrowser.closeDialog(InAppBrowser.java:316)
> W/webview_proxy(27421): at
> org.apache.cordova.core.InAppBrowser.execute(InAppBrowser.java:161)
> W/webview_proxy(27421): at
> org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:65)
> W/webview_proxy(27421): at
> org.apache.cordova.PluginManager.execHelper(PluginManager.java:229)
> W/webview_proxy(27421): at
> org.apache.cordova.PluginManager.exec(PluginManager.java:214)
> W/webview_proxy(27421): at
> org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
> W/webview_proxy(27421): at
> android.os.Handler.dispatchMessage(Handler.java:99)
> W/webview_proxy(27421): at android.os.Looper.loop(Looper.java:137)
> W/webview_proxy(27421): at
> android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:814)
> W/webview_proxy(27421): at java.lang.Thread.run(Thread.java:841)
> W/System.err(27421): java.lang.RuntimeException: java.lang.Throwable:
> Warning: A WebView method was called on thread 'WebViewCoreThread'. All
> WebView methods must be called on the UI thread. Future versions of WebView
> may not support use on other threads.
> W/System.err(27421): at android.webkit.WebView.checkThread(WebView.java:1927)
> W/System.err(27421): at android.webkit.WebView.loadUrl(WebView.java:771)
> W/System.err(27421): at
> org.apache.cordova.core.InAppBrowser.closeDialog(InAppBrowser.java:316)
> W/System.err(27421): at
> org.apache.cordova.core.InAppBrowser.execute(InAppBrowser.java:161)
> W/System.err(27421): at
> org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:65)
> W/System.err(27421): at
> org.apache.cordova.PluginManager.execHelper(PluginManager.java:229)
> W/System.err(27421): at
> org.apache.cordova.PluginManager.exec(PluginManager.java:214)
> W/System.err(27421): at
> org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
> W/System.err(27421): at android.os.Handler.dispatchMessage(Handler.java:99)
> W/System.err(27421): at android.os.Looper.loop(Looper.java:137)
> W/System.err(27421): at
> android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:814)
> W/System.err(27421): at java.lang.Thread.run(Thread.java:841)
> W/System.err(27421): Caused by: java.lang.Throwable: Warning: A WebView
[jira] [Resolved] (CB-4586) Exception when trying to call close() on In-App Browser instance
[
https://issues.apache.org/jira/browse/CB-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-4586.
Resolution: Fixed
Assignee: Joe Bowser
This issue is minor, since it shouldn't actually crash anything.
> Exception when trying to call close() on In-App Browser instance
>
>
> Key: CB-4586
> URL: https://issues.apache.org/jira/browse/CB-4586
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin InAppBrowser
>Affects Versions: 3.0.0
> Environment: Tested on Android 4.3 / Nexus 4 and Nexus 10
>Reporter: Victor Costan
>Assignee: Joe Bowser
>Priority: Minor
>
> Code sketch:
> {code:javascript}
> var browser = window.open(oauthUrl, '_blank', 'location=yes');
> browser.addEventListener('loadstop', function() {
> if (/* event.url matches the OAuth response URL*/ true) {
> browser.close();
> }
> });
> {code}
> Stack trace from adb logcat.
> {code}
> W/webview_proxy(27421): java.lang.Throwable: Warning: A WebView method was
> called on thread 'WebViewCoreThread'. All WebView methods must be called on
> the UI thread. Future versions of WebView may not support use on other
> threads.
> W/webview_proxy(27421): at
> android.webkit.WebView.checkThread(WebView.java:1918)
> W/webview_proxy(27421): at
> android.webkit.WebView.loadUrl(WebView.java:771)
> W/webview_proxy(27421): at
> org.apache.cordova.core.InAppBrowser.closeDialog(InAppBrowser.java:316)
> W/webview_proxy(27421): at
> org.apache.cordova.core.InAppBrowser.execute(InAppBrowser.java:161)
> W/webview_proxy(27421): at
> org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:65)
> W/webview_proxy(27421): at
> org.apache.cordova.PluginManager.execHelper(PluginManager.java:229)
> W/webview_proxy(27421): at
> org.apache.cordova.PluginManager.exec(PluginManager.java:214)
> W/webview_proxy(27421): at
> org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92)
> W/webview_proxy(27421): at
> android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
> W/webview_proxy(27421): at
> android.os.Handler.dispatchMessage(Handler.java:99)
> W/webview_proxy(27421): at android.os.Looper.loop(Looper.java:137)
> W/webview_proxy(27421): at
> android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:814)
> W/webview_proxy(27421): at java.lang.Thread.run(Thread.java:841)
> W/System.err(27421): java.lang.RuntimeException: java.lang.Throwable:
> Warning: A WebView method was called on thread 'WebViewCoreThread'. All
> WebView methods must be called on the UI thread. Future versions of WebView
> may not support use on other threads.
> W/System.err(27421): at android.webkit.WebView.checkThread(WebView.java:1927)
> W/System.err(27421): at android.webkit.WebView.loadUrl(WebView.java:771)
> W/System.err(27421): at
> org.apache.cordova.core.InAppBrowser.closeDialog(InAppBrowser.java:316)
> W/System.err(27421): at
> org.apache.cordova.core.InAppBrowser.execute(InAppBrowser.java:161)
> W/System.err(27421): at
> org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:65)
> W/System.err(27421): at
> org.apache.cordova.PluginManager.execHelper(PluginManager.java:229)
> W/System.err(27421): at
> org.apache.cordova.PluginManager.exec(PluginManager.java:214)
> W/System.err(27421): at
> org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:92)
> W/System.err(27421): at
> android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
> W/System.err(27421): at android.os.Handler.dispatchMessage(Handler.java:99)
> W/System.err(27421): at android.os.Looper.loop(Looper.java:137)
> W/System.err(27421): at
> android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:814)
> W/System.err(27421): at java.lang.Thread.run(Thread.java:841)
> W/System.err(27421): Caused by: java.lang.Throwable: Warning: A WebView
> method was called on thread 'WebViewCoreThread'. All WebView methods must be
> called on the UI thread. Future versions of WebView may not support use on
> other threads.
> W/System.err(27421): at android.webkit.WebV
[jira] [Commented] (CB-3949) Add code fix to broken activity sequence
[
https://issues.apache.org/jira/browse/CB-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752874#comment-13752874
]
Joe Bowser commented on CB-3949:
I think you're overreacting when you call the fix dangerous. Still, I'll remove
the fix.
> Add code fix to broken activity sequence
>
>
> Key: CB-3949
> URL: https://issues.apache.org/jira/browse/CB-3949
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0, 2.8.0
>Reporter: Kuan Yi Ming
>Assignee: Joe Bowser
>Priority: Minor
> Attachments: Cordova281-debug.apk
>
>
> If installing an app via sideloading on Android and opening it immediately
> after install via package installer, going through several pages, then
> pressing Home and later resuming the app later via opening the app from the
> may break the page sequence by creating a new CordovaActivity instance on top
> of the previous one.
> Tested on a Galaxy Nexus, Android 4.2
> Steps to replicate:
> # Copy attached APK over to phone storage and install it.
> # Click 'Open' when the package installer has installed the app, instead of
> clicking 'Done'
> # Press the button in index.html to open the next page.
> # Press Home to pause the app, then reopen the app from the app drawer (not
> the Recent Apps list).
> # The app will relaunch as if it were a new activity instance (showing
> splashscreen again if configured, and adds index.html to the page sequence,
> instead of returning to where the user last was)
> # Pressing back at this index page closes the new CordovaActivity and returns
> to the second page from the previous activity.
> These steps can't be replicated if the app was originally opened in the app
> drawer, a shortcut in the homescreen, or launched via Eclipse's Run button.
> Some bugs filed on Android's issue tracker suggest this can happen by
> clicking 'Open' on apps freshly installed from the Play Store too.
> This probably is an Android issue with the package installer (probably due to
> the package installer calling a non-standard intent) and not PhoneGap, but
> appears to be fixed by using singleTop as the activity launch mode, or adding
> code before calling super.loadUrl() in the activity to check for Intent
> anomalies:
> {code:java}
> Intent intent = getIntent();
> String intentAction = intent.getAction();
> if (!isTaskRoot() && intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
> intentAction != null) {
> if(intentAction.equals(Intent.ACTION_MAIN)) {
> Log.d("Cordova", "This isn't the root activity. Clearing it
> and returning to the root activity.");
> finish();
> return;
> }
> }
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Reopened] (CB-3949) Add code fix to broken activity sequence
[
https://issues.apache.org/jira/browse/CB-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser reopened CB-3949:
Don't like this being reverted, since being able to side-load apps is important
to certain users, that being said, this breaks push notifications.
> Add code fix to broken activity sequence
>
>
> Key: CB-3949
> URL: https://issues.apache.org/jira/browse/CB-3949
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0, 2.8.0
>Reporter: Kuan Yi Ming
>Assignee: Joe Bowser
>Priority: Minor
> Attachments: Cordova281-debug.apk
>
>
> If installing an app via sideloading on Android and opening it immediately
> after install via package installer, going through several pages, then
> pressing Home and later resuming the app later via opening the app from the
> may break the page sequence by creating a new CordovaActivity instance on top
> of the previous one.
> Tested on a Galaxy Nexus, Android 4.2
> Steps to replicate:
> # Copy attached APK over to phone storage and install it.
> # Click 'Open' when the package installer has installed the app, instead of
> clicking 'Done'
> # Press the button in index.html to open the next page.
> # Press Home to pause the app, then reopen the app from the app drawer (not
> the Recent Apps list).
> # The app will relaunch as if it were a new activity instance (showing
> splashscreen again if configured, and adds index.html to the page sequence,
> instead of returning to where the user last was)
> # Pressing back at this index page closes the new CordovaActivity and returns
> to the second page from the previous activity.
> These steps can't be replicated if the app was originally opened in the app
> drawer, a shortcut in the homescreen, or launched via Eclipse's Run button.
> Some bugs filed on Android's issue tracker suggest this can happen by
> clicking 'Open' on apps freshly installed from the Play Store too.
> This probably is an Android issue with the package installer (probably due to
> the package installer calling a non-standard intent) and not PhoneGap, but
> appears to be fixed by using singleTop as the activity launch mode, or adding
> code before calling super.loadUrl() in the activity to check for Intent
> anomalies:
> {code:java}
> Intent intent = getIntent();
> String intentAction = intent.getAction();
> if (!isTaskRoot() && intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
> intentAction != null) {
> if(intentAction.equals(Intent.ACTION_MAIN)) {
> Log.d("Cordova", "This isn't the root activity. Clearing it
> and returning to the root activity.");
> finish();
> return;
> }
> }
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3949) Add code fix to broken activity sequence
[
https://issues.apache.org/jira/browse/CB-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752880#comment-13752880
]
Jason Farnsworth commented on CB-3949:
--
Sorry, I wasn't meaning to be dramatic with my statement. Pragmatically
speaking though, this function seems to test for a condition and then exit the
intent if it doesn't like it. I'm just wondering if there is a way to mitigate
this for the user without dumping them out of the intent.
> Add code fix to broken activity sequence
>
>
> Key: CB-3949
> URL: https://issues.apache.org/jira/browse/CB-3949
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0, 2.8.0
>Reporter: Kuan Yi Ming
>Assignee: Joe Bowser
>Priority: Minor
> Attachments: Cordova281-debug.apk
>
>
> If installing an app via sideloading on Android and opening it immediately
> after install via package installer, going through several pages, then
> pressing Home and later resuming the app later via opening the app from the
> may break the page sequence by creating a new CordovaActivity instance on top
> of the previous one.
> Tested on a Galaxy Nexus, Android 4.2
> Steps to replicate:
> # Copy attached APK over to phone storage and install it.
> # Click 'Open' when the package installer has installed the app, instead of
> clicking 'Done'
> # Press the button in index.html to open the next page.
> # Press Home to pause the app, then reopen the app from the app drawer (not
> the Recent Apps list).
> # The app will relaunch as if it were a new activity instance (showing
> splashscreen again if configured, and adds index.html to the page sequence,
> instead of returning to where the user last was)
> # Pressing back at this index page closes the new CordovaActivity and returns
> to the second page from the previous activity.
> These steps can't be replicated if the app was originally opened in the app
> drawer, a shortcut in the homescreen, or launched via Eclipse's Run button.
> Some bugs filed on Android's issue tracker suggest this can happen by
> clicking 'Open' on apps freshly installed from the Play Store too.
> This probably is an Android issue with the package installer (probably due to
> the package installer calling a non-standard intent) and not PhoneGap, but
> appears to be fixed by using singleTop as the activity launch mode, or adding
> code before calling super.loadUrl() in the activity to check for Intent
> anomalies:
> {code:java}
> Intent intent = getIntent();
> String intentAction = intent.getAction();
> if (!isTaskRoot() && intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
> intentAction != null) {
> if(intentAction.equals(Intent.ACTION_MAIN)) {
> Log.d("Cordova", "This isn't the root activity. Clearing it
> and returning to the root activity.");
> finish();
> return;
> }
> }
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3949) Add code fix to broken activity sequence
[
https://issues.apache.org/jira/browse/CB-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-3949.
Resolution: Won't Fix
Push Notifications beats Side-Loading. This may be revisited at a later time.
> Add code fix to broken activity sequence
>
>
> Key: CB-3949
> URL: https://issues.apache.org/jira/browse/CB-3949
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0, 2.8.0
>Reporter: Kuan Yi Ming
>Assignee: Joe Bowser
>Priority: Minor
> Attachments: Cordova281-debug.apk
>
>
> If installing an app via sideloading on Android and opening it immediately
> after install via package installer, going through several pages, then
> pressing Home and later resuming the app later via opening the app from the
> may break the page sequence by creating a new CordovaActivity instance on top
> of the previous one.
> Tested on a Galaxy Nexus, Android 4.2
> Steps to replicate:
> # Copy attached APK over to phone storage and install it.
> # Click 'Open' when the package installer has installed the app, instead of
> clicking 'Done'
> # Press the button in index.html to open the next page.
> # Press Home to pause the app, then reopen the app from the app drawer (not
> the Recent Apps list).
> # The app will relaunch as if it were a new activity instance (showing
> splashscreen again if configured, and adds index.html to the page sequence,
> instead of returning to where the user last was)
> # Pressing back at this index page closes the new CordovaActivity and returns
> to the second page from the previous activity.
> These steps can't be replicated if the app was originally opened in the app
> drawer, a shortcut in the homescreen, or launched via Eclipse's Run button.
> Some bugs filed on Android's issue tracker suggest this can happen by
> clicking 'Open' on apps freshly installed from the Play Store too.
> This probably is an Android issue with the package installer (probably due to
> the package installer calling a non-standard intent) and not PhoneGap, but
> appears to be fixed by using singleTop as the activity launch mode, or adding
> code before calling super.loadUrl() in the activity to check for Intent
> anomalies:
> {code:java}
> Intent intent = getIntent();
> String intentAction = intent.getAction();
> if (!isTaskRoot() && intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
> intentAction != null) {
> if(intentAction.equals(Intent.ACTION_MAIN)) {
> Log.d("Cordova", "This isn't the root activity. Clearing it
> and returning to the root activity.");
> finish();
> return;
> }
> }
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3949) Add code fix to broken activity sequence
[
https://issues.apache.org/jira/browse/CB-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752884#comment-13752884
]
ASF subversion and git services commented on CB-3949:
-
Commit 5f7ce4b86810f0c8ccc8aa3efaa85b227fadd599 in branch refs/heads/master
from [~bowserj]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=5f7ce4b ]
Reverting CB-3949: Squeay wheel gets the grease
> Add code fix to broken activity sequence
>
>
> Key: CB-3949
> URL: https://issues.apache.org/jira/browse/CB-3949
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0, 2.8.0
>Reporter: Kuan Yi Ming
>Assignee: Joe Bowser
>Priority: Minor
> Attachments: Cordova281-debug.apk
>
>
> If installing an app via sideloading on Android and opening it immediately
> after install via package installer, going through several pages, then
> pressing Home and later resuming the app later via opening the app from the
> may break the page sequence by creating a new CordovaActivity instance on top
> of the previous one.
> Tested on a Galaxy Nexus, Android 4.2
> Steps to replicate:
> # Copy attached APK over to phone storage and install it.
> # Click 'Open' when the package installer has installed the app, instead of
> clicking 'Done'
> # Press the button in index.html to open the next page.
> # Press Home to pause the app, then reopen the app from the app drawer (not
> the Recent Apps list).
> # The app will relaunch as if it were a new activity instance (showing
> splashscreen again if configured, and adds index.html to the page sequence,
> instead of returning to where the user last was)
> # Pressing back at this index page closes the new CordovaActivity and returns
> to the second page from the previous activity.
> These steps can't be replicated if the app was originally opened in the app
> drawer, a shortcut in the homescreen, or launched via Eclipse's Run button.
> Some bugs filed on Android's issue tracker suggest this can happen by
> clicking 'Open' on apps freshly installed from the Play Store too.
> This probably is an Android issue with the package installer (probably due to
> the package installer calling a non-standard intent) and not PhoneGap, but
> appears to be fixed by using singleTop as the activity launch mode, or adding
> code before calling super.loadUrl() in the activity to check for Intent
> anomalies:
> {code:java}
> Intent intent = getIntent();
> String intentAction = intent.getAction();
> if (!isTaskRoot() && intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
> intentAction != null) {
> if(intentAction.equals(Intent.ACTION_MAIN)) {
> Log.d("Cordova", "This isn't the root activity. Clearing it
> and returning to the root activity.");
> finish();
> return;
> }
> }
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3949) Add code fix to broken activity sequence
[
https://issues.apache.org/jira/browse/CB-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752888#comment-13752888
]
Jason Farnsworth commented on CB-3949:
--
Thank you.
> Add code fix to broken activity sequence
>
>
> Key: CB-3949
> URL: https://issues.apache.org/jira/browse/CB-3949
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0, 2.8.0
>Reporter: Kuan Yi Ming
>Assignee: Joe Bowser
>Priority: Minor
> Attachments: Cordova281-debug.apk
>
>
> If installing an app via sideloading on Android and opening it immediately
> after install via package installer, going through several pages, then
> pressing Home and later resuming the app later via opening the app from the
> may break the page sequence by creating a new CordovaActivity instance on top
> of the previous one.
> Tested on a Galaxy Nexus, Android 4.2
> Steps to replicate:
> # Copy attached APK over to phone storage and install it.
> # Click 'Open' when the package installer has installed the app, instead of
> clicking 'Done'
> # Press the button in index.html to open the next page.
> # Press Home to pause the app, then reopen the app from the app drawer (not
> the Recent Apps list).
> # The app will relaunch as if it were a new activity instance (showing
> splashscreen again if configured, and adds index.html to the page sequence,
> instead of returning to where the user last was)
> # Pressing back at this index page closes the new CordovaActivity and returns
> to the second page from the previous activity.
> These steps can't be replicated if the app was originally opened in the app
> drawer, a shortcut in the homescreen, or launched via Eclipse's Run button.
> Some bugs filed on Android's issue tracker suggest this can happen by
> clicking 'Open' on apps freshly installed from the Play Store too.
> This probably is an Android issue with the package installer (probably due to
> the package installer calling a non-standard intent) and not PhoneGap, but
> appears to be fixed by using singleTop as the activity launch mode, or adding
> code before calling super.loadUrl() in the activity to check for Intent
> anomalies:
> {code:java}
> Intent intent = getIntent();
> String intentAction = intent.getAction();
> if (!isTaskRoot() && intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
> intentAction != null) {
> if(intentAction.equals(Intent.ACTION_MAIN)) {
> Log.d("Cordova", "This isn't the root activity. Clearing it
> and returning to the root activity.");
> finish();
> return;
> }
> }
> {code}
--
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: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4697) cordova 3.0.7 couldn't work on mac
Tracy Li created CB-4697: Summary: cordova 3.0.7 couldn't work on mac Key: CB-4697 URL: https://issues.apache.org/jira/browse/CB-4697 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Reporter: Tracy Li Assignee: Filip Maj Steps to reproduce: 1.install the latest cordova-cli 3.0.7 from https://github.com/apache/cordova-cli.git 2.type the following command in the command line $ cordova --version expected: the version number '3.0.7' shows up fact: error: env: node\r: No such file or directory -- 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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4686) env: node\r: No such file or directory when npm publishing on windows (3.0.7)
[ https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benn Mapes updated CB-4686: --- Summary: env: node\r: No such file or directory when npm publishing on windows (3.0.7) (was: env: node\r: No such file or directory on all Cordova commands on new install of 3.0.7) > env: node\r: No such file or directory when npm publishing on windows (3.0.7) > - > > Key: CB-4686 > URL: https://issues.apache.org/jira/browse/CB-4686 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX 10.7.5 >Reporter: Ross James >Assignee: Filip Maj >Priority: Blocker > > All Cordova commands in Mac OSX terminal are now returning: > env: node\r: No such file or directory -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4686) env: node\r: No such file or directory on all Cordova commands on new install of 3.0.7
[ https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753000#comment-13753000 ] Benn Mapes commented on CB-4686: I just republished on a mac as 3.0.8 and it seems to work fine. I'm going to change this to the issue of not being able to publish from npm on windows, and use 3.0.7 as the example. > env: node\r: No such file or directory on all Cordova commands on new install > of 3.0.7 > -- > > Key: CB-4686 > URL: https://issues.apache.org/jira/browse/CB-4686 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX 10.7.5 >Reporter: Ross James >Assignee: Filip Maj >Priority: Blocker > > All Cordova commands in Mac OSX terminal are now returning: > env: node\r: No such file or directory -- 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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4606) Adding geolocation plug-in causes Blackberry10 build to fail
[ https://issues.apache.org/jira/browse/CB-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753003#comment-13753003 ] David Peacock commented on CB-4606: --- This only appears to occur when you have more then 1 plug-in that has a rim-permissions node. For example you will need both the device plug-in and geolocation plug-in to replicate this. > Adding geolocation plug-in causes Blackberry10 build to fail > > > Key: CB-4606 > URL: https://issues.apache.org/jira/browse/CB-4606 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry, CLI, Plugin Geolocation >Affects Versions: 3.0.0 > Environment: Windows 8 >Reporter: David Peacock >Assignee: Lorin Beer > > I created a new Cordova project and added Blackberry10 as a platform. I ran > cordova build and everything was fine. I then added the geolocation plug-in > and tried to build again and received the following error: > [Error: grafting xml at selector "/widget/rim:permissions" from > "C:\SVN\vMobile\ > trunk\platforms\blackberry10\www\config.xml" during config install went bad > :(] > Even more annoying trying to remove the plug-in creates the following error: > [Error: pruning xml at selector "/widget/rim:permissions" from > "C:\SVN\vMobile\t > runk\platforms\blackberry10\www\config.xml" during config uninstall went bad > :(] > To remove I had to remove the blackberry10 platform, remove the geolocation > plug-in then re-add the blackberry10 platform. The underlying issue however > looks to be the same. -- 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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4686) env: node\r: No such file or directory when npm publishing on windows (3.0.7)
[
https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benn Mapes updated CB-4686:
---
Description:
All Cordova commands in Mac OSX terminal return:
{code}
env: node\r: No such file or directory
{code}
When doing an npm publish on a windows machine, due to the '\r' line endings.
was:
All Cordova commands in Mac OSX terminal are now returning:
env: node\r: No such file or directory
> env: node\r: No such file or directory when npm publishing on windows (3.0.7)
> -
>
> Key: CB-4686
> URL: https://issues.apache.org/jira/browse/CB-4686
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
> Environment: Mac OSX 10.7.5
>Reporter: Ross James
>Assignee: Filip Maj
>Priority: Blocker
>
> All Cordova commands in Mac OSX terminal return:
> {code}
> env: node\r: No such file or directory
> {code}
> When doing an npm publish on a windows machine, due to the '\r' line endings.
--
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4686) env: node\r: No such file or directory when npm publishing on windows (3.0.7)
[
https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benn Mapes updated CB-4686:
---
Priority: Major (was: Blocker)
> env: node\r: No such file or directory when npm publishing on windows (3.0.7)
> -
>
> Key: CB-4686
> URL: https://issues.apache.org/jira/browse/CB-4686
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
> Environment: Mac OSX 10.7.5
>Reporter: Ross James
>Assignee: Filip Maj
>
> All Cordova commands in Mac OSX terminal return:
> {code}
> env: node\r: No such file or directory
> {code}
> When doing an npm publish on a windows machine, due to the '\r' line endings.
--
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4686) env: node\r: No such file or directory when npm publishing on windows (3.0.7)
[
https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benn Mapes updated CB-4686:
---
Description:
All Cordova commands in Mac OSX terminal return:
{code}
env: node\r: No such file or directory
{code}
When doing an npm publish on a windows machine, due to the '\r' line endings.
As seen in version 3.0.7 of the cordova CLI.
was:
All Cordova commands in Mac OSX terminal return:
{code}
env: node\r: No such file or directory
{code}
When doing an npm publish on a windows machine, due to the '\r' line endings.
> env: node\r: No such file or directory when npm publishing on windows (3.0.7)
> -
>
> Key: CB-4686
> URL: https://issues.apache.org/jira/browse/CB-4686
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
> Environment: Mac OSX 10.7.5
>Reporter: Ross James
>Assignee: Filip Maj
>
> All Cordova commands in Mac OSX terminal return:
> {code}
> env: node\r: No such file or directory
> {code}
> When doing an npm publish on a windows machine, due to the '\r' line endings.
> As seen in version 3.0.7 of the cordova CLI.
--
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4686) env: node\r: No such file or directory when npm publishing on windows (3.0.7)
[
https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benn Mapes updated CB-4686:
---
Description:
All Cordova commands in Mac OSX terminal return:
{code}
env: node\r: No such file or directory
{code}
When doing an npm publish on a windows machine, due to the '\r' line endings.
As seen in version 3.0.7 of the cordova CLI.
Discussion :
http://markmail.org/search/?q=Published+CLI+3.07+may+have+Windows+line+endings#query:Published%20CLI%203.07%20may%20have%20Windows%20line%20endings+page:1+mid:k53kjf6smupqtuxl+state:results
was:
All Cordova commands in Mac OSX terminal return:
{code}
env: node\r: No such file or directory
{code}
When doing an npm publish on a windows machine, due to the '\r' line endings.
As seen in version 3.0.7 of the cordova CLI.
> env: node\r: No such file or directory when npm publishing on windows (3.0.7)
> -
>
> Key: CB-4686
> URL: https://issues.apache.org/jira/browse/CB-4686
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
> Environment: Mac OSX 10.7.5
>Reporter: Ross James
>Assignee: Filip Maj
>
> All Cordova commands in Mac OSX terminal return:
> {code}
> env: node\r: No such file or directory
> {code}
> When doing an npm publish on a windows machine, due to the '\r' line endings.
> As seen in version 3.0.7 of the cordova CLI.
> Discussion :
> http://markmail.org/search/?q=Published+CLI+3.07+may+have+Windows+line+endings#query:Published%20CLI%203.07%20may%20have%20Windows%20line%20endings+page:1+mid:k53kjf6smupqtuxl+state:results
--
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-4686) env: node\r: No such file or directory when npm publishing on windows (3.0.7)
[
https://issues.apache.org/jira/browse/CB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benn Mapes updated CB-4686:
---
Description:
All Cordova commands in Mac OSX terminal return:
{code}
env: node\r: No such file or directory
{code}
When doing an npm publish on a windows machine, due to the '\r' line endings.
As seen in version 3.0.7 of the cordova CLI.
Discussion : http://markmail.org/message/k53kjf6smupqtuxl
was:
All Cordova commands in Mac OSX terminal return:
{code}
env: node\r: No such file or directory
{code}
When doing an npm publish on a windows machine, due to the '\r' line endings.
As seen in version 3.0.7 of the cordova CLI.
Discussion :
http://markmail.org/search/?q=Published+CLI+3.07+may+have+Windows+line+endings#query:Published%20CLI%203.07%20may%20have%20Windows%20line%20endings+page:1+mid:k53kjf6smupqtuxl+state:results
> env: node\r: No such file or directory when npm publishing on windows (3.0.7)
> -
>
> Key: CB-4686
> URL: https://issues.apache.org/jira/browse/CB-4686
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
> Environment: Mac OSX 10.7.5
>Reporter: Ross James
>Assignee: Filip Maj
>
> All Cordova commands in Mac OSX terminal return:
> {code}
> env: node\r: No such file or directory
> {code}
> When doing an npm publish on a windows machine, due to the '\r' line endings.
> As seen in version 3.0.7 of the cordova CLI.
> Discussion : http://markmail.org/message/k53kjf6smupqtuxl
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4153) Add ability to select default app template at "cordova create" time
[
https://issues.apache.org/jira/browse/CB-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753188#comment-13753188
]
Michal Mocny commented on CB-4153:
--
Been thinking about this one recently. For mobile chrome apps we ended up
using a solution originally proposed by Michael Brooks (and as used in PhoneGap
CLI) -- namely, to pre-create the {app}/.cordova/config.json and set the
{lib:{www:{..}} values.
The issue with doing this from the command line, is that there are (currently)
three parameters: path, id, version. This means with the current proposal we
would need to create command to look like `cordova create --path=... --id=...
--version=...` which I think is just too verbose.
I consider there to be a better alternative: Instead of passing default www
template parameters from the command line, why not just pass the path to a
default config file: `cordova create --config=...`. I think that could have
longer term value, anyway.
> Add ability to select default app template at "cordova create" time
> ---
>
> Key: CB-4153
> URL: https://issues.apache.org/jira/browse/CB-4153
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
>Reporter: Michal Mocny
>Assignee: Filip Maj
>
> Proposal, Implement src flag to cordova create:
> cordova create --src=...
> Where src is:
> * a valid path to a web app
> * from a set of special values, perhaps including:
> - default
> - blank
> - spec
> - easteregg
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4404) android:windowSoftInputMode does not work
[
https://issues.apache.org/jira/browse/CB-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753221#comment-13753221
]
Armno Prom commented on CB-4404:
Your idea of workaround is a good one. I saw some people do another way which
when the keyboard needs to show up, they use native code to force fullscreen to
false and {{adjustResize}} will work.
Thanks for replying Joe!
> android:windowSoftInputMode does not work
> -
>
> Key: CB-4404
> URL: https://issues.apache.org/jira/browse/CB-4404
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.9.0
> Environment: * Mac OS 10.7.5
> * Android 4.1.2 and 4.2.2 emulator using Intel's x86 images
>Reporter: Daniel Trebbien
>Assignee: Joe Bowser
>
> _I recently posted a description of this issue to the phonegap group at
> [https://groups.google.com/d/topic/phonegap/J-h0lt68x0g/discussion]._
> I am testing out PhoneGap 2.9.0 in the Android emulator (using Intel's x86
> images), and I am seeing the issue that the android:windowSoftInputMode
> setting is not having an effect. By default, the setting is set to
> "adjustPan" in the generated project, but when I actually focus a text
> , the soft keyboard appears on top of the app, but does not pan the
> main window, and the is usually hidden beneath the keyboard as a
> result.
> Steps to reproduce:
> # Create a new PhoneGap 2.9.0 project using the {{cordova create}} utility.
> Add the 'android' platform.
> # Open the project in Eclipse.
> # Edit {{index.html}} to add {{ placeholder="Text box">}} below the {{Apache Cordova}} heading.
> # Run the app in Android 4.1.2 or 4.2.2 emulator.
> # Tap the and notice that the soft keyboard is placed over the app
> and the is hidden beneath.
> # Try changing the android:windowSoftInputMode setting in
> {{AndroidManifest.xml}} to "adjustResize", reload the app, and notice that
> the app is not resized when the receives keyboard focus.
> I am seeing this problem in Android 4.1.2 and 4.2.2 emulator. In Android
> 4.0.3 emulator, the app pans as expected.
> The strange thing is that if I load the www/ files in the Browser and focus
> the , then the window is resized to fit the soft keyboard like normal.
> This seems to imply that android:windowSoftInputMode works fine in the
> emulator, but there is some issue in PhoneGap that is preventing it from
> working.
--
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: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2293) File Transfer of picture fails on every other picture
[
https://issues.apache.org/jira/browse/CB-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753360#comment-13753360
]
John Croucher commented on CB-2293:
---
I can confirm it is still an issue in version 3.0.0.
It occurs for me intermittently, on a HTC phone, and any virtual devices.
I have tried the suggested fixes.
- Add System.setProperty("http.keepAlive", "false");
- Remove conn.setRequestProperty("Connection", "Keep-Alive"); from
FileTransfer.java. It already does not exist.
I can also confirm that when the error occurs it is *not* hitting the server at
all, even though it says Sent 15007 of 15007.
08-29 15:06:55.172: D/FileTransfer(531): upload
content://media/external/images/media/14 to
http://exampledomain.com?page=do_upload
08-29 15:06:55.172: D/FileTransfer(531): fileKey: image
08-29 15:06:55.172: D/FileTransfer(531): fileName: 14
08-29 15:06:55.172: D/FileTransfer(531): mimeType: image/jpeg
08-29 15:06:55.172: D/FileTransfer(531): params: {}
08-29 15:06:55.172: D/FileTransfer(531): trustEveryone: true
08-29 15:06:55.172: D/FileTransfer(531): chunkedMode: false
08-29 15:06:55.172: D/FileTransfer(531): headers: null
08-29 15:06:55.172: D/FileTransfer(531): objectId: 1
08-29 15:06:55.172: D/FileTransfer(531): httpMethod: POST
08-29 15:06:55.192: D/FileTransfer(531): Content Length: 15007
08-29 15:06:55.202: D/FileTransfer(531): Sent 15007 of 15007
08-29 15:06:55.202: W/PluginManager(531): THREAD WARNING: exec() call to
FileTransfer.upload blocked the main thread for 54ms. Plugin should use
CordovaInterface.getThreadPool().
08-29 15:06:55.212: W/FileTransfer(531): Error getting HTTP status code from
connection.
08-29 15:06:55.212: W/FileTransfer(531): java.io.EOFException
08-29 15:06:55.212: W/FileTransfer(531):at
com.squareup.okhttp.internal.Util.readAsciiLine(Util.java:314)
08-29 15:06:55.212: W/FileTransfer(531):at
com.squareup.okhttp.internal.http.RawHeaders.fromBytes(RawHeaders.java:301)
08-29 15:06:55.212: W/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpTransport.readResponseHeaders(HttpTransport.java:130)
08-29 15:06:55.212: W/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:630)
08-29 15:06:55.212: W/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:385)
08-29 15:06:55.212: W/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:334)
08-29 15:06:55.212: W/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:534)
08-29 15:06:55.212: W/FileTransfer(531):at
org.apache.cordova.filetransfer.FileTransfer$3.run(FileTransfer.java:444)
08-29 15:06:55.212: W/FileTransfer(531):at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
08-29 15:06:55.212: W/FileTransfer(531):at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
08-29 15:06:55.212: W/FileTransfer(531):at
java.lang.Thread.run(Thread.java:856)
08-29 15:06:55.223: E/FileTransfer(531):
{"target":"http:\/\/exampledomain.com\/?page=do_upload","source":"content:\/\/media\/external\/images\/media\/14","http_status":0,"code":3}
08-29 15:06:55.223: E/FileTransfer(531): java.io.EOFException
08-29 15:06:55.223: E/FileTransfer(531):at
com.squareup.okhttp.internal.Util.readAsciiLine(Util.java:314)
08-29 15:06:55.223: E/FileTransfer(531):at
com.squareup.okhttp.internal.http.RawHeaders.fromBytes(RawHeaders.java:301)
08-29 15:06:55.223: E/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpTransport.readResponseHeaders(HttpTransport.java:130)
08-29 15:06:55.223: E/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:630)
08-29 15:06:55.223: E/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:385)
08-29 15:06:55.223: E/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:334)
08-29 15:06:55.223: E/FileTransfer(531):at
com.squareup.okhttp.internal.http.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:534)
08-29 15:06:55.223: E/FileTransfer(531):at
org.apache.cordova.filetransfer.FileTransfer$3.run(FileTransfer.java:444)
08-29 15:06:55.223: E/FileTransfer(531):at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
08-29 15:06:55.223: E/FileTransfer(531):at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
08-29 15:06:55.223: E/FileTransfer(531):at
java.lang.Thread.run(Thread.java:856)
08-29 15:06:55.223: E/FileTransfer(531): Failed after uploading 15007 of 15007
bytes.
> File Transfer of pi
