[jira] [Commented] (CB-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680966#comment-13680966
]
Joe Bowser commented on CB-3766:
BTW: If you can write a patch before tomorrow, that'd make my life easier,
since you already know what the problem is.
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Native Method)
> {code}
> It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url)
> which reinitialises plugins and spawns a thread to handle potential timeouts.
> My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
> that a timeout has occurred (because the flag loadUrlTimeout does not
> indicate otherwise)
> ---
> I believe my cleanup code onDestroy() is implemented correctly. If not, then
> how should I do it?
> BTW, This same problem did not occur in Cordova v2.4
> More notes:
> * I am suspicious that the problem is introduced by the fix for CB-2458. To
> deliberately cause plugin initialization during destruction seems strange.
> * I am suspicious that the removal of baseUrl in CB-2534, means the CB-2458
> is maybe not even needed anymore, so perhaps original code can be re-instated.
--
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-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser reopened CB-3766:
After re-reading CordovaWebView, you're right. Using loadUrlIntoView is the
absolute wrong thing to do and this makes zero sense, since you're just trying
to execute Javascript in the first place. It should be using loadUrl or
loadUrlNow(). I can't believe we didn't catch it when reviewing this bug.
I'll create a new issue to rename the method, because it should be more obvious
that this initializes the plugins.
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Native Method)
> {code}
> It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url)
> which reinitialises plugins and spawns a thread to handle potential timeouts.
> My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
> that a timeout has occurred (because the flag loadUrlTimeout does not
> indicate otherwise)
> ---
> I believe my cleanup code onDestroy() is implemented correctly. If not, then
> how should I do it?
> BTW, This same problem did not occur in Cordova v2.4
> More notes:
> * I am suspicious that the problem is introduced by the fix for CB-2458. To
> deliberately cause plugin initialization during destruction seems strange.
> * I am suspicious that the removal of baseUrl in CB-2534, means the CB-2458
> is maybe not even needed anymore, so perhaps original code can be re-instated.
--
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-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680870#comment-13680870
]
Peter commented on CB-3766:
---
My environment is: Android-17. Cordova 2.7.0. Galaxy Nexus emulator.
*Re your suggestion that we should just ignore the error in logcat which looks
like "TIMEOUT ERROR":*
Unfortunately, for us it doesn't get as far as saying "TIMEOUT ERROR" because
it fails 1 line before within the me.stopLoading(). Please see the logcat
output in the original post.
*Re your comment "By trying to resolve it the way you're doing, you're causing
it to stack dump":*
In fact, I haven't tried to resolve anything. My code fragment was old code
which previously worked in Cordova 2.4.0.
*Re the test code example:*
I looked at the test code in CordovaWebTestViewActivity. Can you explain why
the line
{code}
cordovaWebView.loadUrl("javascript:try{cordova.require('cordova/channel').onDestroy.fire();}catch(e){console.log('exception
firing destroy event from native');};");
{code}
is there? Isn't that also what the cordovaWebView.handleDestroy() is trying to
do?
*Re is this or is this not a bug:*
I agree perhaps our implementation of onDestroy() is a bit overkill. But the
fact remains that our exact same code previously worked OK for Cordova 2.4.0,
and now for Cordova 2.7.0 it doesn't work. If it looks like a duck and it swims
like a duck and it quacks like a duck then I suggest it is a duck.
*Re my suspicions about CB-2458:*
Do you think plugin initialization (and the accompanying timeout logic) is an
unusual thing to do during handleDestroy() or not? I'm not sure, but that
CB-2458 change from loadUrl to loadUrlIntoView in handleDestroy() seems to have
been the root cause of my trouble.
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Nati
[jira] [Created] (CB-3767) Timers error out when closing an app using CordovaWebView
Joe Bowser created CB-3767: -- Summary: Timers error out when closing an app using CordovaWebView Key: CB-3767 URL: https://issues.apache.org/jira/browse/CB-3767 Project: Apache Cordova Issue Type: Bug Affects Versions: 2.8.0 Reporter: Joe Bowser Priority: Minor Fix For: 2.9.0 See CB-3766 -- 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-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-3766.
Resolution: Incomplete
There needs to be a "OK, this isn't the bug, but it's REALLY, REALLY CLOSE to
the bug!" category, because this JIRA resolution sucks! I guess Incomplete is
the closest one can get?
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Native Method)
> {code}
> It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url)
> which reinitialises plugins and spawns a thread to handle potential timeouts.
> My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
> that a timeout has occurred (because the flag loadUrlTimeout does not
> indicate otherwise)
> ---
> I believe my cleanup code onDestroy() is implemented correctly. If not, then
> how should I do it?
> BTW, This same problem did not occur in Cordova v2.4
> More notes:
> * I am suspicious that the problem is introduced by the fix for CB-2458. To
> deliberately cause plugin initialization during destruction seems strange.
> * I am suspicious that the removal of baseUrl in CB-2534, means the CB-2458
> is maybe not even needed anymore, so perhaps original code can be re-instated.
--
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-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680825#comment-13680825
]
Joe Bowser commented on CB-3766:
OK, there is a bug here. BUT it's the timer issue. Basically, the timers keep
going until they break when the app is closed. By trying to resolve it the way
you're doing, you're causing it to stack dump, but we do need to shut down the
timers after the onDestroy event is done, which is tricky. For now, I'd ignore
the error in logcat, which looks like this:
{code}
06-11 16:44:34.794: E/CordovaWebView(9099): CordovaWebView: TIMEOUT ERROR!
06-11 16:44:50.811: E/CordovaWebView(9099): CordovaWebView: TIMEOUT ERROR!
{code}
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Native Method)
> {code}
> It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url)
> which reinitialises plugins and spawns a thread to handle potential timeouts.
> My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
> that a timeout has occurred (because the flag loadUrlTimeout does not
> indicate otherwise)
> ---
> I believe my cleanup code onDestroy() is implemented correctly. If not, then
> how should I do it?
> BTW, This same problem did not occur in Cordova v2.4
> More notes:
> * I am suspicious that the problem is introduced by the fix for CB-2458. To
> deliberately cause plugin initialization during destruction seems strange.
> * I am suspicious that the removal of baseUrl in CB-2534, means the CB-2458
> is maybe not even needed anymore, so perhaps original code can be re-instated.
--
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-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser reopened CB-3766:
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Native Method)
> {code}
> It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url)
> which reinitialises plugins and spawns a thread to handle potential timeouts.
> My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
> that a timeout has occurred (because the flag loadUrlTimeout does not
> indicate otherwise)
> ---
> I believe my cleanup code onDestroy() is implemented correctly. If not, then
> how should I do it?
> BTW, This same problem did not occur in Cordova v2.4
> More notes:
> * I am suspicious that the problem is introduced by the fix for CB-2458. To
> deliberately cause plugin initialization during destruction seems strange.
> * I am suspicious that the removal of baseUrl in CB-2534, means the CB-2458
> is maybe not even needed anymore, so perhaps original code can be re-instated.
--
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-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-3766.
Resolution: Not A Problem
At first I thought this was a bug, but the more I look at it, this is like
putting on the parking break, then putting your car in drive and then flooring
it! It's going to smell really bad, you'll probably break your parking brake,
and if you smash in a wall, it won't be super obvious that's what you did.
BTW: Our tests are included with CordovaAndroid. We have a test directory for
the native JUnit tests. It includes some interesting examples. I recommend
checking it out if you're going to do CordovaWebView stuff. Also, if you're
finding memory leaks, submit those as bugs, because they ARE bugs.
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Native Method)
> {code}
> It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url)
> which reinitialises plugins and spawns a thread to handle potential timeouts.
> My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
> that a timeout has occurred (because the flag loadUrlTimeout does not
> indicate otherwise)
> ---
> I believe my cleanup code onDestroy() is implemented correctly. If not, then
> how should I do it?
> BTW, This same problem did not occur in Cordova v2.4
> More notes:
> * I am suspicious that the problem is introduced by the fix for CB-2458. To
> deliberately cause plugin initialization during destruction seems strange.
> * I am suspicious that the removal of baseUrl in CB-2534, means the CB-2458
> is maybe not even needed anymore, so perhaps original code can be re-instated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JI
[jira] [Comment Edited] (CB-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680814#comment-13680814
]
Joe Bowser edited comment on CB-3766 at 6/11/13 11:39 PM:
--
You're suspicious of a lot of things, aren't you? :)
Why are you calling pause before destroy? I recommend NOT doing that, since you
need to send the onDestroy event and you can't do that when the timers are shut
down. In fact, the Activity should be able to mop up the mess, and you don't
need to be destroying everything manually.
I have this in our test suite that uses CordovaWebView and it works without a
problem. The firing of onDestroy in JS is handled by handleDestroy():
{code}
@Override
/**
* The final call you receive before your activity is destroyed.
*/
public void onDestroy() {
super.onDestroy();
if (cordovaWebView != null) {
// Send destroy event to JavaScript
cordovaWebView.handleDestroy();
}
}
{code}
We removed baseUrl because we removed our weird broken history shim and we now
use the browser's history once again.
was (Author: bowserj):
You're suspicious of a lot of things, aren't you?
Why are you calling pause before destroy? I recommend NOT doing that, since you
need to send the onDestroy event and you can't do that when the timers are shut
down. In fact, the Activity should be able to mop up the mess, and you don't
need to be destroying everything manually.
I have this in our test suite that uses CordovaWebView and it works without a
problem. The firing of onDestroy in JS is handled by handleDestroy():
{code}
@Override
/**
* The final call you receive before your activity is destroyed.
*/
public void onDestroy() {
super.onDestroy();
if (cordovaWebView != null) {
// Send destroy event to JavaScript
cordovaWebView.handleDestroy();
}
}
{code}
We removed baseUrl because we removed our weird broken history shim and we now
use the browser's history once again.
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(
[jira] [Comment Edited] (CB-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680814#comment-13680814
]
Joe Bowser edited comment on CB-3766 at 6/11/13 11:38 PM:
--
You're suspicious of a lot of things, aren't you?
Why are you calling pause before destroy? I recommend NOT doing that, since you
need to send the onDestroy event and you can't do that when the timers are shut
down. In fact, the Activity should be able to mop up the mess, and you don't
need to be destroying everything manually.
I have this in our test suite that uses CordovaWebView and it works without a
problem. The firing of onDestroy in JS is handled by handleDestroy():
{code}
@Override
/**
* The final call you receive before your activity is destroyed.
*/
public void onDestroy() {
super.onDestroy();
if (cordovaWebView != null) {
// Send destroy event to JavaScript
cordovaWebView.handleDestroy();
}
}
{code}
We removed baseUrl because we removed our weird broken history shim and we now
use the browser's history once again.
was (Author: bowserj):
You're suspicious of a lot of things, aren't you?
Why are you calling pause before destroy? I recommend NOT doing that, since you
need to send the onDestroy event and you can't do that when the timers are shut
down. In fact, the Activity should be able to mop up the mess, and you don't
need to be destroying everything manually.
I have this in our test suite that uses CordovaWebView and it works without a
problem. In fact, we can probably remove the call to Javascript, since that
would be handled by handleDestroy():
{code}
@Override
/**
* The final call you receive before your activity is destroyed.
*/
public void onDestroy() {
super.onDestroy();
if (cordovaWebView != null) {
// Send destroy event to JavaScript
cordovaWebView.loadUrl("javascript:try{cordova.require('cordova/channel').onDestroy.fire();}catch(e){console.log('exception
firing destroy event from native');};");
cordovaWebView.handleDestroy();
}
}
{code}
We removed baseUrl because we removed our weird broken history shim and we now
use the browser's history once again.
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(Ac
[jira] [Commented] (CB-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680814#comment-13680814
]
Joe Bowser commented on CB-3766:
You're suspicious of a lot of things, aren't you?
Why are you calling pause before destroy? I recommend NOT doing that, since you
need to send the onDestroy event and you can't do that when the timers are shut
down. In fact, the Activity should be able to mop up the mess, and you don't
need to be destroying everything manually.
I have this in our test suite that uses CordovaWebView and it works without a
problem. In fact, we can probably remove the call to Javascript, since that
would be handled by handleDestroy():
{code}
@Override
/**
* The final call you receive before your activity is destroyed.
*/
public void onDestroy() {
super.onDestroy();
if (cordovaWebView != null) {
// Send destroy event to JavaScript
cordovaWebView.loadUrl("javascript:try{cordova.require('cordova/channel').onDestroy.fire();}catch(e){console.log('exception
firing destroy event from native');};");
cordovaWebView.handleDestroy();
}
}
{code}
We removed baseUrl because we removed our weird broken history shim and we now
use the browser's history once again.
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Native Method)
> {code}
> It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url)
> which reinitialises plugins and spawns a thread to handle potential timeouts.
> My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
> that a timeout has occurred (because the flag loadUrlTimeout does not
> indicate otherwise)
> ---
> I believe my cleanup code onDestroy() is implemented correctly. If not, then
> how shou
[jira] [Updated] (CB-3766) Introduced bug causes Android stacktrace during cleanup of CordovaWebView
[
https://issues.apache.org/jira/browse/CB-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter updated CB-3766:
--
Summary: Introduced bug causes Android stacktrace during cleanup of
CordovaWebView (was: Introduced bug causes Android stacktrace occurs during
cleanup of CordovaWebView)
> Introduced bug causes Android stacktrace during cleanup of CordovaWebView
> -
>
> Key: CB-3766
> URL: https://issues.apache.org/jira/browse/CB-3766
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Joe Bowser
>
> This was already reprted on the PG Forum, where it was confirmed as a Cordova
> bug.
> https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
> I am using Cordova v2.7.0.
> My Main Android Activity looks like this:
> {code}
> public class MainActivity extends Activity implements CordovaInterface {
> CordovaWebView cwv;
> ...
> //Destruction code is as follows
> @Override
> public void onDestroy() {
> if (cwv != null) {
> cwv.handlePause(true);
> cwv.handleDestroy();
> cwv.removeAllViews();
> cwv.destroy();
> cwv = null;
> }
> super.onDestroy();
> }
> {code}
> After 1st page is rendered, I cause the destroy event by pressing the device
> BACK button.
> This is always resulting in a stacktrace:
> {code}
> 06-11 00:49:57.446: I/Web Console(823): onPause() called at
> file:///android_asset/app1/index.html:11
> 06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on
> inactive InputConnection
> 06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
> 06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
> 06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
> exception (group=0x40a71930)
> 06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
> 06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.webkit.WebView.stopLoading(WebView.java:895)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.handleCallback(Handler.java:725)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Handler.dispatchMessage(Handler.java:92)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.os.Looper.loop(Looper.java:137)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> android.app.ActivityThread.main(ActivityThread.java:5041)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> java.lang.reflect.Method.invoke(Method.java:511)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
> 06-11 00:50:22.334: E/AndroidRuntime(823): at
> dalvik.system.NativeStart.main(Native Method)
> {code}
> It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url)
> which reinitialises plugins and spawns a thread to handle potential timeouts.
> My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
> that a timeout has occurred (because the flag loadUrlTimeout does not
> indicate otherwise)
> ---
> I believe my cleanup code onDestroy() is implemented correctly. If not, then
> how should I do it?
> BTW, This same problem did not occur in Cordova v2.4
> More notes:
> * I am suspicious that the problem is introduced by the fix for CB-2458. To
> deliberately cause plugin initialization during destruction seems strange.
> * I am suspicious that the removal of baseUrl in CB-2534, means the CB-2458
> is maybe not even needed anymore, so perhaps original code can be re-instated.
--
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-3666) Breakout InAppBrowser Plugin for BlackBerry
[ https://issues.apache.org/jira/browse/CB-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer reassigned CB-3666: -- Assignee: Lorin Beer (was: Steve Gill) > Breakout InAppBrowser Plugin for BlackBerry > --- > > Key: CB-3666 > URL: https://issues.apache.org/jira/browse/CB-3666 > Project: Apache Cordova > Issue Type: Improvement > Components: BlackBerry, Plugin InAppBrowser >Reporter: Steve Gill >Assignee: Lorin Beer > Fix For: 3.0.0 > > -- 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-3766) Introduced bug causes Android stacktrace occurs during cleanup of CordovaWebView
Peter created CB-3766:
-
Summary: Introduced bug causes Android stacktrace occurs during
cleanup of CordovaWebView
Key: CB-3766
URL: https://issues.apache.org/jira/browse/CB-3766
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 2.7.0
Reporter: Peter
Assignee: Joe Bowser
This was already reprted on the PG Forum, where it was confirmed as a Cordova
bug.
https://groups.google.com/forum/?fromgroups#!topic/phonegap/NXRvkE8Euls
I am using Cordova v2.7.0.
My Main Android Activity looks like this:
{code}
public class MainActivity extends Activity implements CordovaInterface {
CordovaWebView cwv;
...
//Destruction code is as follows
@Override
public void onDestroy() {
if (cwv != null) {
cwv.handlePause(true);
cwv.handleDestroy();
cwv.removeAllViews();
cwv.destroy();
cwv = null;
}
super.onDestroy();
}
{code}
After 1st page is rendered, I cause the destroy event by pressing the device
BACK button.
This is always resulting in a stacktrace:
{code}
06-11 00:49:57.446: I/Web Console(823): onPause() called at
file:///android_asset/app1/index.html:11
06-11 00:49:58.762: W/IInputConnectionWrapper(823): showStatusIcon on inactive
InputConnection
06-11 00:50:02.222: D/webviewglue(823): nativeDestroy view: 0x2a24bdb0
06-11 00:50:22.292: D/AndroidRuntime(823): Shutting down VM
06-11 00:50:22.292: W/dalvikvm(823): threadid=1: thread exiting with uncaught
exception (group=0x40a71930)
06-11 00:50:22.334: E/AndroidRuntime(823): FATAL EXCEPTION: main
06-11 00:50:22.334: E/AndroidRuntime(823): java.lang.NullPointerException
06-11 00:50:22.334: E/AndroidRuntime(823): at
android.webkit.WebViewClassic.stopLoading(WebViewClassic.java:2645)
06-11 00:50:22.334: E/AndroidRuntime(823): at
android.webkit.WebView.stopLoading(WebView.java:895)
06-11 00:50:22.334: E/AndroidRuntime(823): at
org.apache.cordova.CordovaWebView$2.run(CordovaWebView.java:421)
06-11 00:50:22.334: E/AndroidRuntime(823): at
android.os.Handler.handleCallback(Handler.java:725)
06-11 00:50:22.334: E/AndroidRuntime(823): at
android.os.Handler.dispatchMessage(Handler.java:92)
06-11 00:50:22.334: E/AndroidRuntime(823): at
android.os.Looper.loop(Looper.java:137)
06-11 00:50:22.334: E/AndroidRuntime(823): at
android.app.ActivityThread.main(ActivityThread.java:5041)
06-11 00:50:22.334: E/AndroidRuntime(823): at
java.lang.reflect.Method.invokeNative(Native Method)
06-11 00:50:22.334: E/AndroidRuntime(823): at
java.lang.reflect.Method.invoke(Method.java:511)
06-11 00:50:22.334: E/AndroidRuntime(823): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
06-11 00:50:22.334: E/AndroidRuntime(823): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
06-11 00:50:22.334: E/AndroidRuntime(823): at
dalvik.system.NativeStart.main(Native Method)
{code}
It appears CordovaWebView.handleDestroy() is calling loadUrlIntoView(url) which
reinitialises plugins and spawns a thread to handle potential timeouts.
My stacktrace seems caused by the timeout thread (in CordovaWebView) thinking
that a timeout has occurred (because the flag loadUrlTimeout does not indicate
otherwise)
---
I believe my cleanup code onDestroy() is implemented correctly. If not, then
how should I do it?
BTW, This same problem did not occur in Cordova v2.4
More notes:
* I am suspicious that the problem is introduced by the fix for CB-2458. To
deliberately cause plugin initialization during destruction seems strange.
* I am suspicious that the removal of baseUrl in CB-2534, means the CB-2458 is
maybe not even needed anymore, so perhaps original code can be re-instated.
--
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-3755) CLI not updating platform config files with app version from config.xml
[
https://issues.apache.org/jira/browse/CB-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommy-Carlos Williams reassigned CB-3755:
-
Assignee: Filip Maj (was: Tommy-Carlos Williams)
> CLI not updating platform config files with app version from config.xml
> ---
>
> Key: CB-3755
> URL: https://issues.apache.org/jira/browse/CB-3755
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 2.8.0
>Reporter: Tommy-Carlos Williams
>Assignee: Filip Maj
>
> As an example, when creating a new app, the www/config.xml file has the
> following entry:
> {{ But after {{cordova prepare android}} (as an example) the
> platforms/android/AndroidManifest.xml has:
> {{ It *does* update AndroidManifest.xml with the package from the config.xml,
> but not the version information.
> Even if android:versionName was updated using version from config.xml, there
> would still need to be some provision for android:versionCode
> All of this is also needed for iOS (in AppName-Info.plist) and I would
> imagine the other platforms as well.
--
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-3643) Breakout Globalization Plugin
[ https://issues.apache.org/jira/browse/CB-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680795#comment-13680795 ] Tim Kim commented on CB-3643: - Still need docs and cordova js needs to have globalization ripped out as well. > Breakout Globalization Plugin > - > > Key: CB-3643 > URL: https://issues.apache.org/jira/browse/CB-3643 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Globalization >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > > Breakout the Globalization Plugin for all platforms. -- 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-3718) Breakout Globalization Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680793#comment-13680793 ] Tim Kim commented on CB-3718: - Updated plugin.xml and fixed here: https://github.com/timkim/cordova-plugin-globalization > Breakout Globalization Plugin for Android > - > > Key: CB-3718 > URL: https://issues.apache.org/jira/browse/CB-3718 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Globalization >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- 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-3691) Breakout Geolocation Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680790#comment-13680790 ] Tim Kim commented on CB-3691: - Welp, while the git servers are down I pushed to my github account: https://github.com/timkim/cordova-plugin-geolocation > Breakout Geolocation Plugin for Android > --- > > Key: CB-3691 > URL: https://issues.apache.org/jira/browse/CB-3691 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Geolocation >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- 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-3765) CLI not updating platform config files with app version from config.xml on WP8
Tommy-Carlos Williams created CB-3765:
-
Summary: CLI not updating platform config files with app version
from config.xml on WP8
Key: CB-3765
URL: https://issues.apache.org/jira/browse/CB-3765
Project: Apache Cordova
Issue Type: Sub-task
Components: CLI, WP8
Affects Versions: 2.8.0
Reporter: Tommy-Carlos Williams
Assignee: Filip Maj
During the {{prepare}} stage, the CLI should be updating the version
information in the platform config file(s).
This has been done for Android and iOS but it would be good if someone could do
it for WP8.
See: https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=04648ad
--
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-3764) CLI not updating platform config files with app version from config.xml on WP7
Tommy-Carlos Williams created CB-3764:
-
Summary: CLI not updating platform config files with app version
from config.xml on WP7
Key: CB-3764
URL: https://issues.apache.org/jira/browse/CB-3764
Project: Apache Cordova
Issue Type: Sub-task
Components: CLI, WP7
Affects Versions: 2.8.0
Reporter: Tommy-Carlos Williams
Assignee: Filip Maj
During the {{prepare}} stage, the CLI should be updating the version
information in the platform config file(s).
This has been done for Android and iOS but it would be good if someone could do
it for WP7.
See: https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=04648ad
--
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-3763) CLI not updating platform config files with app version from config.xml on Blackberry
Tommy-Carlos Williams created CB-3763:
-
Summary: CLI not updating platform config files with app version
from config.xml on Blackberry
Key: CB-3763
URL: https://issues.apache.org/jira/browse/CB-3763
Project: Apache Cordova
Issue Type: Sub-task
Components: BlackBerry, CLI
Affects Versions: 2.8.0
Reporter: Tommy-Carlos Williams
Assignee: Lorin Beer
During the {{prepare}} stage, the CLI should be updating the version
information in the platform config file(s).
This has been done for Android and iOS but it would be good if someone could do
it for Blackberry.
See: https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=04648ad
--
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-3671) Breakout Battery Status Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680772#comment-13680772 ] Tim Kim commented on CB-3671: - Tested and looks good. Closing. > Breakout Battery Status Plugin for Android > -- > > Key: CB-3671 > URL: https://issues.apache.org/jira/browse/CB-3671 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Battery Status >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- 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-3671) Breakout Battery Status Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3671. - Resolution: Fixed > Breakout Battery Status Plugin for Android > -- > > Key: CB-3671 > URL: https://issues.apache.org/jira/browse/CB-3671 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Battery Status >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.0.0 > > -- 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-3553) MobileSpec - Media test doesn't check for status constants
[ https://issues.apache.org/jira/browse/CB-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680715#comment-13680715 ] mike billau commented on CB-3553: - Well I was only able to actually see results for this on Nexus 7, Android 4.2.2. It failed spec1 - spec 11, and the final spec, and it did this before Lisa's code...but the good news is that Lisa's test case seemed to work. For all of the other devices, they all failed and actually MobSpec had to force close. They all had generally the same logcat errors too. I think maybe this is because of changes to Android media (eg, all of the DataResource changes.) I was not able to pull the latest changes today since Apache git was down, so there might not be any need for alarm yet. I'll build and test tomorrow with the latest Android build and see if these errors go away. > MobileSpec - Media test doesn't check for status constants > -- > > Key: CB-3553 > URL: https://issues.apache.org/jira/browse/CB-3553 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: media,, test, > Fix For: Master, 2.8.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Media test doesn't check for status constants -- 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-3719) Breakout Globalization Plugin for BlackBerry
[ https://issues.apache.org/jira/browse/CB-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer reassigned CB-3719: -- Assignee: Lorin Beer (was: Steve Gill) > Breakout Globalization Plugin for BlackBerry > > > Key: CB-3719 > URL: https://issues.apache.org/jira/browse/CB-3719 > Project: Apache Cordova > Issue Type: Improvement > Components: BlackBerry, Plugin Globalization >Reporter: Steve Gill >Assignee: Lorin Beer > Fix For: 3.0.0 > > -- 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-3481) MobileSpec - Compass test fails on all tests when device doesn't have compass support
[ https://issues.apache.org/jira/browse/CB-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680691#comment-13680691 ] mike billau commented on CB-3481: - Tested on the following Android devices without any problems. Android 4.2.2 - Nexus 7 (tab) Android 4.0.4 - Galaxy Tab 2, 7.0 Plus (tab) Android 3.0.1 - Motorola Xoom Wifi (tab) Android 2.3.4 - HTC Sensation 4G (phone) Android 2.2 - HTC Evo 4G (phone) Android 2.2 - Galaxy Tab 1, 7.0 (tab) > MobileSpec - Compass test fails on all tests when device doesn't have compass > support > - > > Key: CB-3481 > URL: https://issues.apache.org/jira/browse/CB-3481 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: compass, test > Fix For: 2.7.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > When the compass hardware is not supported on a device all of the compass > related tests will fail. Rather than fail them all, fail the hardware check > and give the user a helpful message as to why the test failed. -- 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-3484) MobileSpec - Camera test doesn't test for cleanup function
[ https://issues.apache.org/jira/browse/CB-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680686#comment-13680686 ] mike billau commented on CB-3484: - Tested on the following Android devices without any issues. Android 4.2.2 - Nexus 7 (tab) Android 4.0.4 - Galaxy Tab 2, 7.0 Plus (tab) Android 3.0.1 - Motorola Xoom Wifi (tab) Android 2.3.4 - HTC Sensation 4G (phone) Android 2.2 - HTC Evo 4G (phone) Android 2.2 - Galaxy Tab 1, 7.0 (tab) > MobileSpec - Camera test doesn't test for cleanup function > -- > > Key: CB-3484 > URL: https://issues.apache.org/jira/browse/CB-3484 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0, 2.8.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: camera,, test, > Fix For: 2.7.0, 2.8.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > The Mobilespec automated test for camera doesn't check for the cleanup > function -- 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-3485) MobileSpec - Device test should include a check for model spec
[ https://issues.apache.org/jira/browse/CB-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680678#comment-13680678 ] mike billau commented on CB-3485: - Tested on the following Android devices. Every device failed test #4 - "Should contain name specification that is a string." If this was deprecated we should remove it from mobile spec; maybe it is just an issue with Android though. Will wait until somebody on iOS can test or someone more knowledgeable can comment ;) Android 4.2.2 - Nexus 7 (tab) Android 4.0.4 - Galaxy Tab 2, 7.0 Plus (tab) Android 3.0.1 - Motorola Xoom Wifi (tab) Android 2.3.4 - HTC Sensation 4G (phone) Android 2.2 - HTC Evo 4G (phone) Android 2.2 - Galaxy Tab 1, 7.0 (tab) > MobileSpec - Device test should include a check for model spec > -- > > Key: CB-3485 > URL: https://issues.apache.org/jira/browse/CB-3485 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0, 2.8.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: device, test, > Fix For: 2.7.0, 2.8.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Device test should include a check for model spec -- 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-3487) MobileSpec - Globalization doesn't test for getPreferredLanguage
[ https://issues.apache.org/jira/browse/CB-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680671#comment-13680671 ] mike billau commented on CB-3487: - Tested on the following Android devices without a problem, except for the 2.2 devices which both fail spec20 - spec 24: Android 4.2.2 - Nexus 7 (tab) Android 4.0.4 - Galaxy Tab 2, 7.0 Plus (tab) Android 3.0.1 - Motorola Xoom Wifi (tab) Android 2.3.4 - HTC Sensation 4G (phone) Android 2.2 - HTC Evo 4G (phone) Android 2.2 - Galaxy Tab 1, 7.0 (tab) > MobileSpec - Globalization doesn't test for getPreferredLanguage > > > Key: CB-3487 > URL: https://issues.apache.org/jira/browse/CB-3487 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0, 2.8.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: globalization, test, > Fix For: 2.7.0, 2.8.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Globalization doesn't test for getPreferredLanguage -- 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-3488) MobileSpec - Globalization doesn't check for constants
[ https://issues.apache.org/jira/browse/CB-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680655#comment-13680655 ] mike billau commented on CB-3488: - Tested on the following Android devices, everything worked fine*, and the tests failed successfully when I commented out the relevant code in cordova.js Android 4.2.2 - Nexus 7 (tab) Android 4.0.4 - Galaxy Tab 2, 7.0 Plus (tab) Android 3.0.1 - Motorola Xoom Wifi (tab) Android 2.3.4 - HTC Sensation 4G (phone) Android 2.2 - HTC Evo 4G (phone) * Android 2.2 - Galaxy Tab 1, 7.0 (tab) * *Note, both of the Android 2.2 devices that I tested failed the same 5 tests (spec 20 - 24). Since it was two different devices on the same OS, presumably this is a problem with Android 2.2. > MobileSpec - Globalization doesn't check for constants > -- > > Key: CB-3488 > URL: https://issues.apache.org/jira/browse/CB-3488 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0, 2.8.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: globalization, test, > Fix For: 2.7.0, 2.8.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Globalzation doesn't check for constants -- 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-3489) MobileSpec - There is no automated test for splashscreen
[ https://issues.apache.org/jira/browse/CB-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680625#comment-13680625 ] mike billau commented on CB-3489: - Tested with the following Android devices and did not see any problems: Android 4.2.2 - Nexus 7 (tab) Android 4.0.4 - Galaxy Tab 2, 7.0 Plus (tab) Android 3.0.1 - Motorola Xoom Wifi (tab) Android 2.3.4 - HTC Sensation 4G (phone) Android 2.2 - HTC Evo 4G (phone) Android 2.2 - Galaxy Tab 1, 7.0 (tab) > MobileSpec - There is no automated test for splashscreen > > > Key: CB-3489 > URL: https://issues.apache.org/jira/browse/CB-3489 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0, 2.8.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Fix For: 2.7.0, 2.8.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - There is no automated test for splashscreen -- 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-2406) write binary to disk
[ https://issues.apache.org/jira/browse/CB-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680622#comment-13680622 ] Ian Clelland commented on CB-2406: -- I have this working in iOS, with a patch ready for as soon as the git repos come back up. The general idea in JavaScript is to detect incoming blobs in FileWriter.write(), convert them to ArrayBuffers, and then use the native capabilities of the bridge to transfer the ArrayBuffer contents to native code. The native side (FileUtils|CDVFile).write() method then needs to be updated then to accept binary data as well as strings, and to save it to disk in that raw format, without performing any Unicode conversion on it. > write binary to disk > > > Key: CB-2406 > URL: https://issues.apache.org/jira/browse/CB-2406 > Project: Apache Cordova > Issue Type: New Feature >Reporter: James Campos >Assignee: Ian Clelland > > i'd like to write binary data to disk. i realize that this may be difficult > due to the native bridge, but it is possible by requiring that the data be > hex or base64 encoded, or by treating javascript strings as arrays of 16 bit > integers -- 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-2406) write binary to disk
[ https://issues.apache.org/jira/browse/CB-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland reassigned CB-2406: Assignee: Ian Clelland (was: Andrew Grieve) > write binary to disk > > > Key: CB-2406 > URL: https://issues.apache.org/jira/browse/CB-2406 > Project: Apache Cordova > Issue Type: New Feature >Reporter: James Campos >Assignee: Ian Clelland > > i'd like to write binary data to disk. i realize that this may be difficult > due to the native bridge, but it is possible by requiring that the data be > hex or base64 encoded, or by treating javascript strings as arrays of 16 bit > integers -- 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-3491) MobileSpec - Storage test should check for openDatabase function
[ https://issues.apache.org/jira/browse/CB-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680613#comment-13680613 ] mike billau commented on CB-3491: - Updated mobile spec with the added test case, tested on the following Android devices and did not see any problems: Android 4.2.2 - Nexus 7 (tab) Android 4.0.4 - Galaxy Tab 2, 7.0 Plus (tab) Android 3.0.1 - Motorola Xoom Wifi (tab) Android 2.3.4 - HTC Sensation 4G (phone) Android 2.2 - HTC Evo 4G (phone) Android 2.2 - Galaxy Tab 1, 7.0 (tab) > MobileSpec - Storage test should check for openDatabase function > > > Key: CB-3491 > URL: https://issues.apache.org/jira/browse/CB-3491 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0, 2.8.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: storage, test, > Fix For: 2.7.0, 2.8.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Storage test should check for openDatabase function -- 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-3742) CLI 'serve' command fails with 'cannot call method update_project' of undefined
[ https://issues.apache.org/jira/browse/CB-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680604#comment-13680604 ] Dan Moore commented on CB-3742: --- Thanks! > CLI 'serve' command fails with 'cannot call method update_project' of > undefined > --- > > Key: CB-3742 > URL: https://issues.apache.org/jira/browse/CB-3742 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 2.8.0 > Environment: I'm running 64 bit CentOS6.4 in virtual box (host system > is windows 7). > I'm using node 0.10.10, jdk 1.7, ant 1.8, the latest and greatest android sdk > 22.0.1/version 17 of the build and platform tools). cordova --version > returns 2.8.13. > I have a colleague who is running macos 10.7.5 who received the same error > for 'cordova serve ios' >Reporter: Dan Moore >Assignee: Filip Maj > Fix For: 2.9.0 > > > I've successfully installed cordova-cli (thanks for this, by the way!) and > can create a project and add the android platform. > These all work: > 'cordova create kewlapp kewlapp' > 'cordova -d platform android' > 'cordova build android' > The emulator works (with a started 2.3.3 emulator): > 'cordova emulate android' > However, when I run 'cordova serve android' I get this error: > [TypeError: Cannot call method 'update_project' of undefined] > 'cordova -d serve android' has the same output. > From digging around in the node src, it seems that the parser created on line > 125 of node_modules/cordova/src/serve.js is undefined for some reason. I > can't imagine why, though I did notice that node_modules/cordova/platforms.js > has the android url pointing to cordova-ios.git. Changing that to > android.git didn't resolve the issue. -- 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-3664) Breakout InAppBrowser Plugin for ios
[ https://issues.apache.org/jira/browse/CB-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong reassigned CB-3664: - Assignee: Herm Wong (was: Steve Gill) > Breakout InAppBrowser Plugin for ios > > > Key: CB-3664 > URL: https://issues.apache.org/jira/browse/CB-3664 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS, Plugin InAppBrowser >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3664) Breakout InAppBrowser Plugin for ios
[ https://issues.apache.org/jira/browse/CB-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong resolved CB-3664. --- Resolution: Fixed > Breakout InAppBrowser Plugin for ios > > > Key: CB-3664 > URL: https://issues.apache.org/jira/browse/CB-3664 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS, Plugin InAppBrowser >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3760) Plugman iOS Framework - Escaping
[
https://issues.apache.org/jira/browse/CB-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680605#comment-13680605
]
Tim Davis commented on CB-3760:
---
Hi,
I was working in a command line environment someone else setup. 0.5.5 was
there. I see the commit history for the xcode that 0.6 and higher would have
the necessary fix 2012/10/30.
> Plugman iOS Framework - Escaping
>
>
> Key: CB-3760
> URL: https://issues.apache.org/jira/browse/CB-3760
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
> Environment: Mac osx, Cordova 2.2
>Reporter: Tim Davis
>Assignee: Filip Maj
>
>
> yields something like this in the .pbxproj file:
> 1C101F74A326484C91C4223B /* libstdc++.dylib */ = {isa = PBXFileReference;
> fileEncoding = 4; lastKnownFileType = "compiled.mach-o.dylib"; name =
> libstdc++.dylib; path = usr/lib/libstdc++.dylib; sourceTree = SDKROOT; };
> This results in an invalid xcode project which can't be opened. This should
> result in something like this
> 1C101F74A326484C91C4223B /* libstdc++.dylib */ = {isa = PBXFileReference;
> fileEncoding = 4; lastKnownFileType = "compiled.mach-o.dylib"; name =
> "libstdc++.dylib"; path = "usr/lib/libstdc++.dylib"; sourceTree = SDKROOT; };
>
> You see the name and path are encapsulated in "" marks.
--
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-3665) Breakout InAppBrowser Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong resolved CB-3665. --- Resolution: Fixed > Breakout InAppBrowser Plugin for Android > > > Key: CB-3665 > URL: https://issues.apache.org/jira/browse/CB-3665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin InAppBrowser >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3665) Breakout InAppBrowser Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong reassigned CB-3665: - Assignee: Herm Wong (was: Steve Gill) > Breakout InAppBrowser Plugin for Android > > > Key: CB-3665 > URL: https://issues.apache.org/jira/browse/CB-3665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin InAppBrowser >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3660) Breakout Vibration Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong resolved CB-3660. --- Resolution: Fixed > Breakout Vibration Plugin for Android > - > > Key: CB-3660 > URL: https://issues.apache.org/jira/browse/CB-3660 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Vibration >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3660) Breakout Vibration Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong reassigned CB-3660: - Assignee: Herm Wong (was: Steve Gill) > Breakout Vibration Plugin for Android > - > > Key: CB-3660 > URL: https://issues.apache.org/jira/browse/CB-3660 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Vibration >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3659) Breakout Vibration Plugin for ios
[ https://issues.apache.org/jira/browse/CB-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong reassigned CB-3659: - Assignee: Herm Wong (was: Steve Gill) > Breakout Vibration Plugin for ios > - > > Key: CB-3659 > URL: https://issues.apache.org/jira/browse/CB-3659 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS, Plugin Vibration >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3659) Breakout Vibration Plugin for ios
[ https://issues.apache.org/jira/browse/CB-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong resolved CB-3659. --- Resolution: Fixed > Breakout Vibration Plugin for ios > - > > Key: CB-3659 > URL: https://issues.apache.org/jira/browse/CB-3659 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS, Plugin Vibration >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3647) Breakout Device Motion Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong resolved CB-3647. --- Resolution: Fixed device motion no longer requires explicit permissions in Android. > Breakout Device Motion Plugin for Android > - > > Key: CB-3647 > URL: https://issues.apache.org/jira/browse/CB-3647 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Device Motion >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3647) Breakout Device Motion Plugin for Android
[ https://issues.apache.org/jira/browse/CB-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herm Wong reassigned CB-3647: - Assignee: Herm Wong (was: Steve Gill) > Breakout Device Motion Plugin for Android > - > > Key: CB-3647 > URL: https://issues.apache.org/jira/browse/CB-3647 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Device Motion >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.0.0 > > -- 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-3508) camera plugin
[
https://issues.apache.org/jira/browse/CB-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680582#comment-13680582
]
Steve Gill commented on CB-3508:
Is it safe for me to make DirectoryManager.getTempDirectoryPath public on the
3.0.0 branch?
> camera plugin
> -
>
> Key: CB-3508
> URL: https://issues.apache.org/jira/browse/CB-3508
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, iOS, Plugin Camera
>Reporter: Steve Gill
>Assignee: Steve Gill
> Fix For: 3.0.0
>
>
> This is all to do with 3.0.0 branch stuff and Plugin breakout
> ios
> Create a cordova project. Run, device ready fire. Instal the plugin and
> device ready won't fire.
> Something wrong with how it installs or handles dependencies. I believe it
> has to do with the javascript. More investigating required.
> Android
> Lots of build issues post installation (below). Need to fix imports and look
> at dependencies.
> After these issues are sorted, android could have same issue as ios
> -compile:
> [javac] Compiling 4 source files to
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/bin/classes
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:29:
> package org.apache.commons.codec.binary does not exist
> [javac] import org.apache.commons.codec.binary.Base64;
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:522:
> cannot find symbol
> [javac] symbol : class ExifHelper
> [javac] location: class org.apache.cordova.core.CameraLauncher
> [javac] private Bitmap getRotatedBitmap(int rotate, Bitmap bitmap, ExifHelper
> exif) {
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:216:
> getTempDirectoryPath(android.content.Context) has protected access in
> org.apache.cordova.DirectoryManager
> [javac] photo = new
> File(DirectoryManager.getTempDirectoryPath(this.cordova.getActivity()),
> ".Pic.jpg");
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:218:
> getTempDirectoryPath(android.content.Context) has protected access in
> org.apache.cordova.DirectoryManager
> [javac] photo = new
> File(DirectoryManager.getTempDirectoryPath(this.cordova.getActivity()),
> ".Pic.png");
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:279:
> cannot find symbol
> [javac] symbol : class ExifHelper
> [javac] location: class org.apache.cordova.core.CameraLauncher
> [javac] ExifHelper exif = new ExifHelper();
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:279:
> cannot find symbol
> [javac] symbol : class ExifHelper
> [javac] location: class org.apache.cordova.core.CameraLauncher
> [javac] ExifHelper exif = new ExifHelper();
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:282:
> getTempDirectoryPath(android.content.Context) has protected access in
> org.apache.cordova.DirectoryManager
> [javac]
> exif.createInFile(DirectoryManager.getTempDirectoryPath(this.cordova.getActivity())
> + "/.Pic.jpg");
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:325:
> getTempDirectoryPath(android.content.Context) has protected access in
> org.apache.cordova.DirectoryManager
> [javac] uri = Uri.fromFile(new
> File(DirectoryManager.getTempDirectoryPath(this.cordova.getActivity()),
> System.currentTimeMillis() + ".jpg"));
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:447:
> getTempDirectoryPath(android.content.Context) has protected access in
> org.apache.cordova.DirectoryManager
> [javac] String resizePath =
> DirectoryManager.getTempDirectoryPath(this.cordova.getActivity()) +
> "/resize.jpg";
> [javac] ^
> [javac]
> /Users/stevengill/Documents/repo/plugins/plugin-breakout-release-test-harness/cameraandroid/src/org/apache/cordova/core/CameraLauncher.java:451:
> cannot find symbol
> [javac] symbol : class ExifHelper
> [javac] location: class org.apache.cordova.core.CameraLauncher
> [
[jira] [Commented] (CB-3760) Plugman iOS Framework - Escaping
[
https://issues.apache.org/jira/browse/CB-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680580#comment-13680580
]
Filip Maj commented on CB-3760:
---
For the record, the latest plugman uses the latest version of that library
(I/we are all contributors to it). What version of plugman were you using when
you had the issue?
> Plugman iOS Framework - Escaping
>
>
> Key: CB-3760
> URL: https://issues.apache.org/jira/browse/CB-3760
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
> Environment: Mac osx, Cordova 2.2
>Reporter: Tim Davis
>Assignee: Filip Maj
>
>
> yields something like this in the .pbxproj file:
> 1C101F74A326484C91C4223B /* libstdc++.dylib */ = {isa = PBXFileReference;
> fileEncoding = 4; lastKnownFileType = "compiled.mach-o.dylib"; name =
> libstdc++.dylib; path = usr/lib/libstdc++.dylib; sourceTree = SDKROOT; };
> This results in an invalid xcode project which can't be opened. This should
> result in something like this
> 1C101F74A326484C91C4223B /* libstdc++.dylib */ = {isa = PBXFileReference;
> fileEncoding = 4; lastKnownFileType = "compiled.mach-o.dylib"; name =
> "libstdc++.dylib"; path = "usr/lib/libstdc++.dylib"; sourceTree = SDKROOT; };
>
> You see the name and path are encapsulated in "" marks.
--
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-3762) notification.prompt doesn't accept an empty string for default text
Todd Miller created CB-3762: --- Summary: notification.prompt doesn't accept an empty string for default text Key: CB-3762 URL: https://issues.apache.org/jira/browse/CB-3762 Project: Apache Cordova Issue Type: Bug Components: Plugin Dialogs Affects Versions: 2.7.0, 2.8.0 Reporter: Todd Miller Assignee: Steve Gill Priority: Minor Specifying "" as the last parameter for navigator.notification.prompt, the prompt dialog will still show "Default Text" in the text input box. However, putting a string of just a single space works (but also results in a space in the text box). In additional seems like the default of "Default Text" isn't the best choice from UX perspective. A default of an empty text box would make more sense. Changing line 5909 in cordova.js from: var _defaultText = (defaultText || "Default text"); to var _defaultText = (defaultText || ""); Resolves the issue and gives a blank text box by default. Documentation would also need to be updated with the new default if this is adopted. -- 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-3760) Plugman iOS Framework - Escaping
[
https://issues.apache.org/jira/browse/CB-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Davis resolved CB-3760.
---
Resolution: Fixed
found this was resolved by current version of node module xcode.
https://github.com/alunny/node-xcode
> Plugman iOS Framework - Escaping
>
>
> Key: CB-3760
> URL: https://issues.apache.org/jira/browse/CB-3760
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
> Environment: Mac osx, Cordova 2.2
>Reporter: Tim Davis
>Assignee: Filip Maj
>
>
> yields something like this in the .pbxproj file:
> 1C101F74A326484C91C4223B /* libstdc++.dylib */ = {isa = PBXFileReference;
> fileEncoding = 4; lastKnownFileType = "compiled.mach-o.dylib"; name =
> libstdc++.dylib; path = usr/lib/libstdc++.dylib; sourceTree = SDKROOT; };
> This results in an invalid xcode project which can't be opened. This should
> result in something like this
> 1C101F74A326484C91C4223B /* libstdc++.dylib */ = {isa = PBXFileReference;
> fileEncoding = 4; lastKnownFileType = "compiled.mach-o.dylib"; name =
> "libstdc++.dylib"; path = "usr/lib/libstdc++.dylib"; sourceTree = SDKROOT; };
>
> You see the name and path are encapsulated in "" marks.
--
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-3758) "cordova emulate android" not working as expected
[ https://issues.apache.org/jira/browse/CB-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680529#comment-13680529 ] Mike Sierra commented on CB-3758: - Thanks; emulator works now. To clarify the intended usage: when running "emulate" with no emulator currently running, will an AVD be assigned by default? Also, note the confusing output I received: a build file missing followed by a "build failed" error, then downstream a "BUILD SUCCEEDED." > "cordova emulate android" not working as expected > - > > Key: CB-3758 > URL: https://issues.apache.org/jira/browse/CB-3758 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 2.8.0 > Environment: Mac >Reporter: Mike Sierra >Assignee: Filip Maj > > Output from my test "abc" project: > ulothrix:pg sierra$ cd abc/ > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] > ulothrix:abc sierra$ ls platforms/ > android > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] > ulothrix:abc sierra$ cordova build android > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] -- 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-3761) XHR Crash using Cordova
Dillon Lucente created CB-3761: -- Summary: XHR Crash using Cordova Key: CB-3761 URL: https://issues.apache.org/jira/browse/CB-3761 Project: Apache Cordova Issue Type: Bug Components: WP8 Affects Versions: 2.8.0 Environment: Windows 8, Visual Studio 11, WP Simulator and Device Reporter: Dillon Lucente Assignee: Jesse MacFadyen Out of bounds crash when trying to use Cordova.js overridden XHR. Affected files: FileUtil.cs (readResourceAsText() line 707) and Cordova.js (line 6258) Changes in the C# implementation haven't made their way back to the js implementation. readResourceAsText() expects an array of 5 elements, but the js is only supplying two arguments. Possible fixes: Change line 6258 of Cordova.js from: "File", "readResourceAsText", [alias._url] to: "File", "readResourceAsText", [alias._url, "", 0, 0] Or change readResourceAsText() to not try to assign variables it doesn't use. -- 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-3521) MobileSpec - Battery autotest should verify batterystatus property object
[ https://issues.apache.org/jira/browse/CB-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680515#comment-13680515 ] mike billau commented on CB-3521: - Tested on the following Android devices and levels. Everything seemed fine, the devices all reported success for both tests, and they all successfully failed when I commented out the relevant code in cordova.js - it all looks good to me. Android 4.2.2 - Nexus 7 (tab) Android 4.0.4 - Galaxy Tab 2, 7.0 Plus (tab) Android 3.0.1 - Motorola Xoom Wifi (tab) Android 2.3.4 - HTC Sensation 4G (phone) Android 2.2 - HTC Evo 4G (phone) Android 2.2 - Galaxy Tab 1, 7.0 (tab) > MobileSpec - Battery autotest should verify batterystatus property object > - > > Key: CB-3521 > URL: https://issues.apache.org/jira/browse/CB-3521 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Affects Versions: 2.7.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: battery, test, > Fix For: 2.8.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Battery autotest should verify batterystatus property object -- 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-3760) Plugman iOS Framework - Escaping
Tim Davis created CB-3760:
-
Summary: Plugman iOS Framework - Escaping
Key: CB-3760
URL: https://issues.apache.org/jira/browse/CB-3760
Project: Apache Cordova
Issue Type: Bug
Components: Plugman
Environment: Mac osx, Cordova 2.2
Reporter: Tim Davis
Assignee: Filip Maj
yields something like this in the .pbxproj file:
1C101F74A326484C91C4223B /* libstdc++.dylib */ = {isa = PBXFileReference;
fileEncoding = 4; lastKnownFileType = "compiled.mach-o.dylib"; name =
libstdc++.dylib; path = usr/lib/libstdc++.dylib; sourceTree = SDKROOT; };
This results in an invalid xcode project which can't be opened. This should
result in something like this
1C101F74A326484C91C4223B /* libstdc++.dylib */ = {isa = PBXFileReference;
fileEncoding = 4; lastKnownFileType = "compiled.mach-o.dylib"; name =
"libstdc++.dylib"; path = "usr/lib/libstdc++.dylib"; sourceTree = SDKROOT; };
You see the name and path are encapsulated in "" marks.
--
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-3306) Lazy-load Device Platforms in CLI
[ https://issues.apache.org/jira/browse/CB-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj updated CB-3306: -- Fix Version/s: (was: 3.0.0) 2.9.0 > Lazy-load Device Platforms in CLI > - > > Key: CB-3306 > URL: https://issues.apache.org/jira/browse/CB-3306 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI >Reporter: Andrew Grieve >Assignee: Filip Maj >Priority: Critical > Fix For: 2.9.0 > > > As per ML discussion: http://callback.markmail.org/thread/zurpjsjdxv3m5ogh > Let's delete the checked in versions of cordova-android, cordova-ios, > cordova-blackberry. Instead, they should be downloaded to: > ~/.cordova/platforms/cordova-FOO > the first time they are required. -- 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-3756) Camera.getPicture fails when choosing from photo library
[ https://issues.apache.org/jira/browse/CB-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Woghiren updated CB-3756: - Assignee: Lorin Beer (was: Shazron Abdullah) > Camera.getPicture fails when choosing from photo library > > > Key: CB-3756 > URL: https://issues.apache.org/jira/browse/CB-3756 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.8.0 >Reporter: Ville Karavirta >Assignee: Lorin Beer > > In v2.8.0 on iOS, choosing a photo from library fails always and calls the > error callback with message "(null)". > As far as I could debug it, it fails on line 343 of CDVCamera.m due to data > being null. Reason seems to be that on line 310, the > UIImageJPEGRepresentation is assigned to self.data and nothing is ever > assigned to data. -- 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-3759) InAppBrowser - ability to not show back/forward/Done buttons
Lindsey Simon created CB-3759: - Summary: InAppBrowser - ability to not show back/forward/Done buttons Key: CB-3759 URL: https://issues.apache.org/jira/browse/CB-3759 Project: Apache Cordova Issue Type: Bug Reporter: Lindsey Simon Priority: Minor I'm using the InAppBrowser to popup a browser to do OAuth. During that process I don't want the user to be confused by more buttons - and they are not buttons they can use anyway. I simply want to be able to show the URL bar so that they don't think I'm phishing their account, so showing more URL bar (i.e. full width) would be even better. -- 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-3750) InAppBrowser: Can We Haz Loading Spinner?
[ https://issues.apache.org/jira/browse/CB-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lindsey Simon updated CB-3750: -- Priority: Trivial (was: Major) > InAppBrowser: Can We Haz Loading Spinner? > - > > Key: CB-3750 > URL: https://issues.apache.org/jira/browse/CB-3750 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 2.5.0, 2.6.0, 2.7.0, 2.8.0 > Environment: Android (at least) >Reporter: Lindsey Simon >Assignee: Steve Gill >Priority: Trivial > > I'm using the InAppBrowser to open a Google/Facebook OAuth login screen. In > order for that to work it first opens an URL on my server and then redirects > to the proper provider endpoint. > When the internet is slow this results in a pretty lousy user experience as > the InAppBrowser doesn't seem to have any loading indicator - which made me > think it wasn't working, and then I clicked Done prematurely. I suspect my > users will do the same and not try a second time and my app is DOA. > Am I missing anything here by chance? > Any advice on how to get a loading indicator in the least-intrusive way? -- 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-3626) ./bin/lib/start-emulator with no id parameter does nothing
[
https://issues.apache.org/jira/browse/CB-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-3626:
--
Fix Version/s: 2.9.0
Assignee: Filip Maj (was: Benn Mapes)
Setting for 2.9 and assigning to myself.
> ./bin/lib/start-emulator with no id parameter does nothing
> --
>
> Key: CB-3626
> URL: https://issues.apache.org/jira/browse/CB-3626
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.8.0
> Environment: Mac OSX 10.7.5
>Reporter: Filip Maj
>Assignee: Filip Maj
> Fix For: 2.9.0
>
>
> According to the [Command Line Design wiki
> document|http://wiki.apache.org/cordova/CommandLineToolingDesign], running
> {{start-emulator}} with no parameters should start the first available
> emulator.
> In my particular case, if I run {{list-emulator-images}}, I get the following
> output:
> {code}
> debug_rake_android15
> Gingerbread
> ICS
> {code}
> However, running {{start-emulator}} with no ID results in the script exiting
> with 0 status code and doing nothing. Running {{start-emulator ICS}}, so with
> a valid emulator ID, works as expected.
--
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-3758) "cordova emulate android" not working as expected
[
https://issues.apache.org/jira/browse/CB-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-3758:
--
Summary: "cordova emulate android" not working as expected (was: "ripple
android" doesn't work)
Changing the title of issue to reflect the current issue being discussed.
I think these are problems with the underlying, project-level scripts. The
following two issues are related:
CB-3627
CB-3626
Essentially, the above two issues prevent the cordova-cli command {{cordova
emulate android}} from starting an emulator before attempting to deploy to it
(and thus your error).
However, if you start the emulator manually, it should work. I just tried on my
machine and the following worked as expected:
{code}
$ cordova create tmp
$ cd tmp
$ cordova platform add android
$ cd platforms/android
$ ./cordova/lib/list-emulator-images
ICS
$ ./cordova/lib/start-emulator ICS
$ cordova -d emulate android
* some output snipped *
BUILD SUCCESSFUL
Total time: 14 seconds
Installing
/Users/fil/src/tmp/platforms/android/bin/HelloCordova-debug-unaligned.apk onto
emulator-5554...
2257 KB/s (7103530 bytes in 3.072s)
pkg: /data/local/tmp/HelloCordova-debug-unaligned.apk
Success
Launching application...
Starting: Intent { act=android.intent.action.MAIN
cmp=io.cordova.hellocordova/.HelloCordova }
Status: ok
Activity: io.cordova.hellocordova/.HelloCordova
ThisTime: 1515
TotalTime: 1515
Complete
Platform "android" deployed to emulator.
{code}
> "cordova emulate android" not working as expected
> -
>
> Key: CB-3758
> URL: https://issues.apache.org/jira/browse/CB-3758
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 2.8.0
> Environment: Mac
>Reporter: Mike Sierra
>Assignee: Filip Maj
>
> Output from my test "abc" project:
> ulothrix:pg sierra$ cd abc/
> ulothrix:abc sierra$ cordova ripple android
> [TypeError: Cannot call method 'update_project' of undefined]
> ulothrix:abc sierra$ ls platforms/
> android
> ulothrix:abc sierra$ cordova ripple android
> [TypeError: Cannot call method 'update_project' of undefined]
> ulothrix:abc sierra$ cordova build android
> ulothrix:abc sierra$ cordova ripple android
> [TypeError: Cannot call method 'update_project' of undefined]
--
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-3627) ./cordova/run --emulator does not start emulator image
[
https://issues.apache.org/jira/browse/CB-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-3627:
--
Fix Version/s: 2.9.0
Assignee: Filip Maj (was: Benn Mapes)
Setting for 2.9 and assigning to myself.
> ./cordova/run --emulator does not start emulator image
> --
>
> Key: CB-3627
> URL: https://issues.apache.org/jira/browse/CB-3627
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 2.8.0
> Environment: Mac OSX 10.7.5
>Reporter: Filip Maj
>Assignee: Filip Maj
> Fix For: 2.9.0
>
>
> Running
> {code}
> $ ./cordova/run --emulator
> {code}
> Successfully builds the project, but eventually stops with the following
> output:
> {code}
> No emulators found to deploy to. Please make sure your emulator is started
> and you can view it using the 'cordova/lib/list-started-emulators' command.
> {code}
> Per the [Command Line Design
> document|http://wiki.apache.org/cordova/CommandLineToolingDesign] (see the
> section about multi-device flow near the top), when calling {{run}} with an
> emulator as a target, the {{run}} script should call {{start-emulator}} with
> the first available ID _if no emulator is currently running_.
--
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-3758) "ripple android" doesn't work
[ https://issues.apache.org/jira/browse/CB-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680449#comment-13680449 ] Mike Sierra commented on CB-3758: - Note the comment. It works now after rolling back to 2.8.0, then re-updating to the current version. But may still be a bug. BTW, another minor prob. When running either "cordova emulate android" or "cordova run android", I get an error: Cleaning project... Buildfile: build.xml does not exist! Build failed Buildfile: /Users/sierra/sandbox/pg/abc/platforms/android/build.xml ...but at the end of the debug stream: BUILD SUCCESSFUL Total time: 4 seconds No emulators found to deploy to. Please make sure your emulator is started and you can view it using the 'cordova/lib/list-started-emulators' command. ] I ran the android command & have an emulator running, but it's unclear how to make the cordova command aware of it. Any idea? --Mike S > "ripple android" doesn't work > - > > Key: CB-3758 > URL: https://issues.apache.org/jira/browse/CB-3758 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 2.8.0 > Environment: Mac >Reporter: Mike Sierra >Assignee: Filip Maj > > Output from my test "abc" project: > ulothrix:pg sierra$ cd abc/ > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] > ulothrix:abc sierra$ ls platforms/ > android > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] > ulothrix:abc sierra$ cordova build android > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] -- 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-3758) "ripple android" doesn't work
[ https://issues.apache.org/jira/browse/CB-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj updated CB-3758: -- Component/s: (was: Android) Assignee: Filip Maj (was: Joe Bowser) I'll take a look. > "ripple android" doesn't work > - > > Key: CB-3758 > URL: https://issues.apache.org/jira/browse/CB-3758 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 2.8.0 > Environment: Mac >Reporter: Mike Sierra >Assignee: Filip Maj > > Output from my test "abc" project: > ulothrix:pg sierra$ cd abc/ > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] > ulothrix:abc sierra$ ls platforms/ > android > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] > ulothrix:abc sierra$ cordova build android > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] -- 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-3741) [BlackBerry10] Integration tests failing for target and create scripts
[ https://issues.apache.org/jira/browse/CB-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680429#comment-13680429 ] Lorin Beer commented on CB-3741: require more more information for this to be a valid bug report: 1. what exactly is failing 2. steps to replicate closing until the above is provided > [BlackBerry10] Integration tests failing for target and create scripts > -- > > Key: CB-3741 > URL: https://issues.apache.org/jira/browse/CB-3741 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Reporter: Daniel Audino >Assignee: Lorin Beer > Fix For: 2.9.0 > > > Multiple integration test failures for create and target scripts -- 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-3741) [BlackBerry10] Integration tests failing for target and create scripts
[ https://issues.apache.org/jira/browse/CB-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer resolved CB-3741. Resolution: Cannot Reproduce will be reopened if actual error/failure is specified > [BlackBerry10] Integration tests failing for target and create scripts > -- > > Key: CB-3741 > URL: https://issues.apache.org/jira/browse/CB-3741 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Reporter: Daniel Audino >Assignee: Lorin Beer > Fix For: 2.9.0 > > > Multiple integration test failures for create and target scripts -- 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-3758) "ripple android" doesn't work
[ https://issues.apache.org/jira/browse/CB-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680432#comment-13680432 ] Mike Sierra commented on CB-3758: - Correction: it didn't work under the latest version 2.8.14. I rolled back to 2.8.0, and I got the same results. Then I updated back to 2.8.14, and it works fine. > "ripple android" doesn't work > - > > Key: CB-3758 > URL: https://issues.apache.org/jira/browse/CB-3758 > Project: Apache Cordova > Issue Type: Bug > Components: Android, CLI >Affects Versions: 2.8.0 > Environment: Mac >Reporter: Mike Sierra >Assignee: Joe Bowser > > Output from my test "abc" project: > ulothrix:pg sierra$ cd abc/ > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] > ulothrix:abc sierra$ ls platforms/ > android > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] > ulothrix:abc sierra$ cordova build android > ulothrix:abc sierra$ cordova ripple android > [TypeError: Cannot call method 'update_project' of undefined] -- 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-3758) "ripple android" doesn't work
Mike Sierra created CB-3758: --- Summary: "ripple android" doesn't work Key: CB-3758 URL: https://issues.apache.org/jira/browse/CB-3758 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Affects Versions: 2.8.0 Environment: Mac Reporter: Mike Sierra Assignee: Joe Bowser Output from my test "abc" project: ulothrix:pg sierra$ cd abc/ ulothrix:abc sierra$ cordova ripple android [TypeError: Cannot call method 'update_project' of undefined] ulothrix:abc sierra$ ls platforms/ android ulothrix:abc sierra$ cordova ripple android [TypeError: Cannot call method 'update_project' of undefined] ulothrix:abc sierra$ cordova build android ulothrix:abc sierra$ cordova ripple android [TypeError: Cannot call method 'update_project' of undefined] -- 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-3757) navigator.camera.getPicture(...) doesn't work on IOS with the PHOTOLIBRARY
Ronny Schleicher created CB-3757:
Summary: navigator.camera.getPicture(...) doesn't work on IOS with
the PHOTOLIBRARY
Key: CB-3757
URL: https://issues.apache.org/jira/browse/CB-3757
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera
Affects Versions: 2.8.0
Environment: Can be reproduce on all iOS Devices and the iOS-Simulator.
Reporter: Ronny Schleicher
Assignee: Steve Gill
Priority: Critical
Since the Cordova version 2.8.0 it is not possible to load images from the
photo library on the iOS (Device and Simulator).
Following code always calls the function onGetPictureFailed. An error analysis
is not possible in the callback, as the callback is called with no parameters!
Note: in the Cordova 2.7.0 follow code works fine.
navigator.camera.getPicture(
onGetPictureSuccessfully,
onGetPictureFailed,
{
quality: 90,
destinationType: navigator.camera.DestinationType.FILE_URI,
sourceType :navigator.camera.PictureSourceType.PHOTOLIBRARY,
correctOrientation : true,
targetWidth: 800,
targetHeight : 800
});
--
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-3756) Camera.getPicture fails when choosing from photo library
Ville Karavirta created CB-3756: --- Summary: Camera.getPicture fails when choosing from photo library Key: CB-3756 URL: https://issues.apache.org/jira/browse/CB-3756 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 2.8.0 Reporter: Ville Karavirta Assignee: Shazron Abdullah In v2.8.0 on iOS, choosing a photo from library fails always and calls the error callback with message "(null)". As far as I could debug it, it fails on line 343 of CDVCamera.m due to data being null. Reason seems to be that on line 310, the UIImageJPEGRepresentation is assigned to self.data and nothing is ever assigned to data. -- 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-3351) Support for mutual SSL (on Ajax calls)
[ https://issues.apache.org/jira/browse/CB-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680364#comment-13680364 ] Tommy-Carlos Williams commented on CB-3351: --- I am currently looking into client certificate authentication for our app, and my research so far has led me to believe that, at least on Android, this would be unlikely to be a good fit for inclusion in Cordova. There is a project to provide client certificate authentication to the Android webView[1], but it is hindered by requiring access to private APIs in Android 4.x[2] iOS might be able to handle it with a plugin rather than a modification of Cordova itself, but I have not looked into it very deeply yet. At least on iOS I know that it is possible with native NSUrlConnections. [1] https://github.com/yonekawa/webview-with-client-certificate [2] https://github.com/yonekawa/webview-with-client-certificate#android-4x > Support for mutual SSL (on Ajax calls) > --- > > Key: CB-3351 > URL: https://issues.apache.org/jira/browse/CB-3351 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, BlackBerry, WP8 >Affects Versions: 2.6.0 >Reporter: Eloy Gonzalez > Labels: clientcertificate, mutualSSL, ssl > > In some situations, two-factor authentication is required, and client > certificates (a X.509 certificate with a 1.3.6.1.5.5.7.3.2 enhanced key > usage) are a popular choice as a first factor. With mutual SSL, the client > verifies the server's identity (server authentication) and the server > verifies the client's identity (client authentication). Unfortunately, > Cordova does not support mutual SSL. > This issue is relate to CB-2669, but not only for iOS -- 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-3755) CLI not updating platform config files with app version from config.xml
[
https://issues.apache.org/jira/browse/CB-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680312#comment-13680312
]
ASF subversion and git services commented on CB-3755:
-
Commit 04648ad00a2e2601f4052ca9da90377f54f9dbcd in branch refs/heads/master2
from [~devgeeks]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=04648ad ]
[CB-3755] Update platform version from config.xml
- Updates AndroidManifest.xml android:versionName with version from config.xml
- Updates AppName-Info.plist CFBundleVersion with version from config.xml
NOTE: So far this is only handling Android and iOS. WP7/8 and Blackberry need
to be updated as well
> CLI not updating platform config files with app version from config.xml
> ---
>
> Key: CB-3755
> URL: https://issues.apache.org/jira/browse/CB-3755
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 2.8.0
>Reporter: Tommy-Carlos Williams
>Assignee: Tommy-Carlos Williams
>
> As an example, when creating a new app, the www/config.xml file has the
> following entry:
> {{ But after {{cordova prepare android}} (as an example) the
> platforms/android/AndroidManifest.xml has:
> {{ It *does* update AndroidManifest.xml with the package from the config.xml,
> but not the version information.
> Even if android:versionName was updated using version from config.xml, there
> would still need to be some provision for android:versionCode
> All of this is also needed for iOS (in AppName-Info.plist) and I would
> imagine the other platforms as well.
--
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
