[jira] [Comment Edited] (CB-10338) getCurrentPosition() hangs on Android 4.2.2
[
https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234090#comment-15234090
]
Zhang Zengbo edited comment on CB-10338 at 4/10/16 1:58 PM:
I am not sure if I am facing the same problem of this. I am testing this api
(getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I
just tested on outdoor, and it always report timeout error (I set timeout to 30
seconds and test the api every minutes ) until I start another app :
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
from the position service, I can see that the cordova app is using location
service in low-battery mode, but com.chartcross.gpstest is in high-battery mode.
Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation
2.1.0 .
the most important test code ( I am using ionic with ngCordova):
{code:javascript}
function updateLocation(){
var options = {
enableHighAccuracy: true,
timeout: 3
};
$cordovaGeolocation.getCurrentPosition(options).then(function(r) {
console.log(JSON.stringify(r));
$scope.currentLocation = r;
}, function(e) {
console.log(e);
$scope.currentLocation = angular.copy(errLocation);
});
}
{code}
was (Author: pluswave):
I am not sure if I am facing the same problem of this. I am testing this api
(getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I
just tested on outdoor, and it always report timeout error (I set timeout to 30
seconds and test the api every minutes ) until I start another app :
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
from the position service, I can see that the cordova app is using location
service in low-battery mode, but com.chartcross.gpstest is in high-battery mode.
Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation
2.1.0 .
the most important test code ( I am using ionic with ngCordova):
{code}
function updateLocation(){
var options = {
enableHighAccuracy: true,
timeout: 3
};
$cordovaGeolocation.getCurrentPosition(options).then(function(r) {
console.log(JSON.stringify(r));
$scope.currentLocation = r;
}, function(e) {
console.log(e);
$scope.currentLocation = angular.copy(errLocation);
});
}
{code}
> getCurrentPosition() hangs on Android 4.2.2
>
>
> Key: CB-10338
> URL: https://issues.apache.org/jira/browse/CB-10338
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Geolocation
>Affects Versions: 2.0.0
> Environment: Android 4.2.2 (running cordova-android@5.0.0)
>Reporter: Tom Nightingale
>Priority: Trivial
> Labels: android, reproduced, triaged
>
> Neither success or error callbacks are called after calling
> navigator.geolocation.getCurrentPosition().
> Stepping through the plugin with Chrome's Javascript debugger and Android
> Studio's Java debugger shows that the plugin's shim code successfully
> executes the Geolocation 'getPermission' check and returns back to fire the
> shim's success handler (line 31
> [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]).
> However the next line which appears to call the platform's native
> getCurrentPosition() just hangs; neither the provided success or error
> callbacks are called. If I try step into that function call with the Chrome
> remote debugger it just jumps to the end of the executing function (line 36 @
> above link). It's as if getCurrentPosition() is a no-op. Chrome's "show
> function definition" functionality isn't able to resolve the definition
> either.
> I wonder if the bug is somewhere in the cordova/modulemapper code? This is an
> area of Cordova I am not familiar with...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-10338) getCurrentPosition() hangs on Android 4.2.2
[
https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234090#comment-15234090
]
Zhang Zengbo edited comment on CB-10338 at 4/10/16 1:56 PM:
I am not sure if I am facing the same problem of this. I am testing this api
(getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I
just tested on outdoor, and it always report timeout error (I set timeout to 30
seconds and test the api every minutes ) until I start another app :
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
from the position service, I can see that the cordova app is using location
service in low-battery mode, but com.chartcross.gpstest is in high-battery mode.
Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation
2.1.0 .
the most important test code ( I am using ionic with ngCordova):
{code}
function updateLocation(){
var options = {
enableHighAccuracy: true,
timeout: 3
};
$cordovaGeolocation.getCurrentPosition(options).then(function(r) {
console.log(JSON.stringify(r));
$scope.currentLocation = r;
}, function(e) {
console.log(e);
$scope.currentLocation = angular.copy(errLocation);
});
}
{code}
was (Author: pluswave):
I am not sure if I am facing the same problem of this. I am testing this api
(getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I
just tested on outdoor, and it always report timeout error (I set timeout to 30
seconds and test the api every minutes ) until I start another app :
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
from the position service, I can see that the cordova app is using location
service in low-battery mode, but com.chartcross.gpstest is in high-battery mode.
Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation
2.1.0 .
the most important test code ( I am using ionic with ngCordova):
{quote}
function updateLocation(){
var options = {
enableHighAccuracy: true,
timeout: 3
};
$cordovaGeolocation.getCurrentPosition(options).then(function(r) {
console.log(JSON.stringify(r));
$scope.currentLocation = r;
}, function(e) {
console.log(e);
$scope.currentLocation = angular.copy(errLocation);
});
}
{quote}
> getCurrentPosition() hangs on Android 4.2.2
>
>
> Key: CB-10338
> URL: https://issues.apache.org/jira/browse/CB-10338
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Geolocation
>Affects Versions: 2.0.0
> Environment: Android 4.2.2 (running cordova-android@5.0.0)
>Reporter: Tom Nightingale
>Priority: Trivial
> Labels: android, reproduced, triaged
>
> Neither success or error callbacks are called after calling
> navigator.geolocation.getCurrentPosition().
> Stepping through the plugin with Chrome's Javascript debugger and Android
> Studio's Java debugger shows that the plugin's shim code successfully
> executes the Geolocation 'getPermission' check and returns back to fire the
> shim's success handler (line 31
> [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]).
> However the next line which appears to call the platform's native
> getCurrentPosition() just hangs; neither the provided success or error
> callbacks are called. If I try step into that function call with the Chrome
> remote debugger it just jumps to the end of the executing function (line 36 @
> above link). It's as if getCurrentPosition() is a no-op. Chrome's "show
> function definition" functionality isn't able to resolve the definition
> either.
> I wonder if the bug is somewhere in the cordova/modulemapper code? This is an
> area of Cordova I am not familiar with...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-10338) getCurrentPosition() hangs on Android 4.2.2
[
https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234090#comment-15234090
]
Zhang Zengbo edited comment on CB-10338 at 4/10/16 1:55 PM:
I am not sure if I am facing the same problem of this. I am testing this api
(getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I
just tested on outdoor, and it always report timeout error (I set timeout to 30
seconds and test the api every minutes ) until I start another app :
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
from the position service, I can see that the cordova app is using location
service in low-battery mode, but com.chartcross.gpstest is in high-battery mode.
Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation
2.1.0 .
the most important test code ( I am using ionic with ngCordova):
{quote}
function updateLocation(){
var options = {
enableHighAccuracy: true,
timeout: 3
};
$cordovaGeolocation.getCurrentPosition(options).then(function(r) {
console.log(JSON.stringify(r));
$scope.currentLocation = r;
}, function(e) {
console.log(e);
$scope.currentLocation = angular.copy(errLocation);
});
}
{quote}
was (Author: pluswave):
I am not sure if I am facing the same problem of this. I am testing this api
(getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I
just tested on outdoor, and it always report timeout error (I set timeout to 30
seconds and test the api every minutes ) until I start another app :
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
from the position service, I can see that the cordova app is using location
service in low-battery mode, but com.chartcross.gpstest is in high-battery mode.
Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation
2.1.0 .
the most important test code ( I am using ionic with ngCordova):
function updateLocation(){
var options = {
enableHighAccuracy: true,
timeout: 3
};
$cordovaGeolocation.getCurrentPosition(options).then(function(r) {
console.log(JSON.stringify(r));
$scope.currentLocation = r;
}, function(e) {
console.log(e);
$scope.currentLocation = angular.copy(errLocation);
});
}
> getCurrentPosition() hangs on Android 4.2.2
>
>
> Key: CB-10338
> URL: https://issues.apache.org/jira/browse/CB-10338
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Geolocation
>Affects Versions: 2.0.0
> Environment: Android 4.2.2 (running cordova-android@5.0.0)
>Reporter: Tom Nightingale
>Priority: Trivial
> Labels: android, reproduced, triaged
>
> Neither success or error callbacks are called after calling
> navigator.geolocation.getCurrentPosition().
> Stepping through the plugin with Chrome's Javascript debugger and Android
> Studio's Java debugger shows that the plugin's shim code successfully
> executes the Geolocation 'getPermission' check and returns back to fire the
> shim's success handler (line 31
> [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]).
> However the next line which appears to call the platform's native
> getCurrentPosition() just hangs; neither the provided success or error
> callbacks are called. If I try step into that function call with the Chrome
> remote debugger it just jumps to the end of the executing function (line 36 @
> above link). It's as if getCurrentPosition() is a no-op. Chrome's "show
> function definition" functionality isn't able to resolve the definition
> either.
> I wonder if the bug is somewhere in the cordova/modulemapper code? This is an
> area of Cordova I am not familiar with...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-10338) getCurrentPosition() hangs on Android 4.2.2
[
https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234090#comment-15234090
]
Zhang Zengbo edited comment on CB-10338 at 4/10/16 1:53 PM:
I am not sure if I am facing the same problem of this. I am testing this api
(getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I
just tested on outdoor, and it always report timeout error (I set timeout to 30
seconds and test the api every minutes ) until I start another app :
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
from the position service, I can see that the cordova app is using location
service in low-battery mode, but com.chartcross.gpstest is in high-battery mode.
Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation
2.1.0 .
the most important test code ( I am using ionic with ngCordova):
function updateLocation(){
var options = {
enableHighAccuracy: true,
timeout: 3
};
$cordovaGeolocation.getCurrentPosition(options).then(function(r) {
console.log(JSON.stringify(r));
$scope.currentLocation = r;
}, function(e) {
console.log(e);
$scope.currentLocation = angular.copy(errLocation);
});
}
was (Author: pluswave):
I am not sure if I am facing the same problem of this. I am testing this api
(getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I
just tested on outdoor, and it always report timeout error until I start
another app :
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
from the position service, I can see that the cordova app is using location
service in low-battery mode, but com.chartcross.gpstest is in high-battery mode.
Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation
2.1.0 .
> getCurrentPosition() hangs on Android 4.2.2
>
>
> Key: CB-10338
> URL: https://issues.apache.org/jira/browse/CB-10338
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Geolocation
>Affects Versions: 2.0.0
> Environment: Android 4.2.2 (running cordova-android@5.0.0)
>Reporter: Tom Nightingale
>Priority: Trivial
> Labels: android, reproduced, triaged
>
> Neither success or error callbacks are called after calling
> navigator.geolocation.getCurrentPosition().
> Stepping through the plugin with Chrome's Javascript debugger and Android
> Studio's Java debugger shows that the plugin's shim code successfully
> executes the Geolocation 'getPermission' check and returns back to fire the
> shim's success handler (line 31
> [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]).
> However the next line which appears to call the platform's native
> getCurrentPosition() just hangs; neither the provided success or error
> callbacks are called. If I try step into that function call with the Chrome
> remote debugger it just jumps to the end of the executing function (line 36 @
> above link). It's as if getCurrentPosition() is a no-op. Chrome's "show
> function definition" functionality isn't able to resolve the definition
> either.
> I wonder if the bug is somewhere in the cordova/modulemapper code? This is an
> area of Cordova I am not familiar with...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-10338) getCurrentPosition() hangs on Android 4.2.2
[ https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234123#comment-15234123 ] Zhang Zengbo edited comment on CB-10338 at 4/10/16 1:48 PM: same issue as I tested on same Nexus4 Device but this time android version 5.1.1 (after flash this image: https://dl.google.com/dl/android/aosp/occam-lmy48t-factory-416938f1.tgz) . only one difference: this time from location settings both apps show "high battery usage". was (Author: pluswave): same issue as I tested on same Nexus4 Device but this time android version 5.1.1 (after flash this image: https://dl.google.com/dl/android/aosp/occam-lmy48t-factory-416938f1.tgz) . only one difference: this time from location settings two apps shows "high battery usage". > getCurrentPosition() hangs on Android 4.2.2 > > > Key: CB-10338 > URL: https://issues.apache.org/jira/browse/CB-10338 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Geolocation >Affects Versions: 2.0.0 > Environment: Android 4.2.2 (running cordova-android@5.0.0) >Reporter: Tom Nightingale >Priority: Trivial > Labels: android, reproduced, triaged > > Neither success or error callbacks are called after calling > navigator.geolocation.getCurrentPosition(). > Stepping through the plugin with Chrome's Javascript debugger and Android > Studio's Java debugger shows that the plugin's shim code successfully > executes the Geolocation 'getPermission' check and returns back to fire the > shim's success handler (line 31 > [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]). > However the next line which appears to call the platform's native > getCurrentPosition() just hangs; neither the provided success or error > callbacks are called. If I try step into that function call with the Chrome > remote debugger it just jumps to the end of the executing function (line 36 @ > above link). It's as if getCurrentPosition() is a no-op. Chrome's "show > function definition" functionality isn't able to resolve the definition > either. > I wonder if the bug is somewhere in the cordova/modulemapper code? This is an > area of Cordova I am not familiar with... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10338) getCurrentPosition() hangs on Android 4.2.2
[ https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234123#comment-15234123 ] Zhang Zengbo commented on CB-10338: --- same issue as I tested on same Nexus4 Device but this time android version 5.1.1 (after flash this image: https://dl.google.com/dl/android/aosp/occam-lmy48t-factory-416938f1.tgz) . only one difference: this time from location settings two apps shows "high battery usage". > getCurrentPosition() hangs on Android 4.2.2 > > > Key: CB-10338 > URL: https://issues.apache.org/jira/browse/CB-10338 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Geolocation >Affects Versions: 2.0.0 > Environment: Android 4.2.2 (running cordova-android@5.0.0) >Reporter: Tom Nightingale >Priority: Trivial > Labels: android, reproduced, triaged > > Neither success or error callbacks are called after calling > navigator.geolocation.getCurrentPosition(). > Stepping through the plugin with Chrome's Javascript debugger and Android > Studio's Java debugger shows that the plugin's shim code successfully > executes the Geolocation 'getPermission' check and returns back to fire the > shim's success handler (line 31 > [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]). > However the next line which appears to call the platform's native > getCurrentPosition() just hangs; neither the provided success or error > callbacks are called. If I try step into that function call with the Chrome > remote debugger it just jumps to the end of the executing function (line 36 @ > above link). It's as if getCurrentPosition() is a no-op. Chrome's "show > function definition" functionality isn't able to resolve the definition > either. > I wonder if the bug is somewhere in the cordova/modulemapper code? This is an > area of Cordova I am not familiar with... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-10338) getCurrentPosition() hangs on Android 4.2.2
[ https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234090#comment-15234090 ] Zhang Zengbo edited comment on CB-10338 at 4/10/16 12:38 PM: - I am not sure if I am facing the same problem of this. I am testing this api (getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I just tested on outdoor, and it always report timeout error until I start another app : https://play.google.com/store/apps/details?id=com.chartcross.gpstest from the position service, I can see that the cordova app is using location service in low-battery mode, but com.chartcross.gpstest is in high-battery mode. Btw: software versions are cordova-android 5.1.1 and cordova-plugin-geoloation 2.1.0 . was (Author: pluswave): I am not sure if I am facing the same problem of this. I am testing this api (getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I just tested on outdoor, and it always report timeout error until I start another app : https://play.google.com/store/apps/details?id=com.chartcross.gpstest from the position service, I can see that the cordova app is using location service in low-battery mode, but com.chartcross.gpstest is in high-battery mode. > getCurrentPosition() hangs on Android 4.2.2 > > > Key: CB-10338 > URL: https://issues.apache.org/jira/browse/CB-10338 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Geolocation >Affects Versions: 2.0.0 > Environment: Android 4.2.2 (running cordova-android@5.0.0) >Reporter: Tom Nightingale >Priority: Trivial > Labels: android, reproduced, triaged > > Neither success or error callbacks are called after calling > navigator.geolocation.getCurrentPosition(). > Stepping through the plugin with Chrome's Javascript debugger and Android > Studio's Java debugger shows that the plugin's shim code successfully > executes the Geolocation 'getPermission' check and returns back to fire the > shim's success handler (line 31 > [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]). > However the next line which appears to call the platform's native > getCurrentPosition() just hangs; neither the provided success or error > callbacks are called. If I try step into that function call with the Chrome > remote debugger it just jumps to the end of the executing function (line 36 @ > above link). It's as if getCurrentPosition() is a no-op. Chrome's "show > function definition" functionality isn't able to resolve the definition > either. > I wonder if the bug is somewhere in the cordova/modulemapper code? This is an > area of Cordova I am not familiar with... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10338) getCurrentPosition() hangs on Android 4.2.2
[ https://issues.apache.org/jira/browse/CB-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234090#comment-15234090 ] Zhang Zengbo commented on CB-10338: --- I am not sure if I am facing the same problem of this. I am testing this api (getCurrentPosition) on a Nexus4 Device with stock 4.4 version from Google. I just tested on outdoor, and it always report timeout error until I start another app : https://play.google.com/store/apps/details?id=com.chartcross.gpstest from the position service, I can see that the cordova app is using location service in low-battery mode, but com.chartcross.gpstest is in high-battery mode. > getCurrentPosition() hangs on Android 4.2.2 > > > Key: CB-10338 > URL: https://issues.apache.org/jira/browse/CB-10338 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Geolocation >Affects Versions: 2.0.0 > Environment: Android 4.2.2 (running cordova-android@5.0.0) >Reporter: Tom Nightingale >Priority: Trivial > Labels: android, reproduced, triaged > > Neither success or error callbacks are called after calling > navigator.geolocation.getCurrentPosition(). > Stepping through the plugin with Chrome's Javascript debugger and Android > Studio's Java debugger shows that the plugin's shim code successfully > executes the Geolocation 'getPermission' check and returns back to fire the > shim's success handler (line 31 > [here|https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=blob;f=www/android/geolocation.js;h=82e3582e0c225340db44add8fe3ea81256dff03f;hb=57eb4dc550a3d88d3ebbb60a0d6a83d61f898dd7#l31]). > However the next line which appears to call the platform's native > getCurrentPosition() just hangs; neither the provided success or error > callbacks are called. If I try step into that function call with the Chrome > remote debugger it just jumps to the end of the executing function (line 36 @ > above link). It's as if getCurrentPosition() is a no-op. Chrome's "show > function definition" functionality isn't able to resolve the definition > either. > I wonder if the bug is somewhere in the cordova/modulemapper code? This is an > area of Cordova I am not familiar with... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-3397) A way to control the width/height and x/y placement of the InAppBrowser UIWebView on the screen
[ https://issues.apache.org/jira/browse/CB-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743085#comment-14743085 ] Zhang Zengbo commented on CB-3397: -- If I understand correctly, the inappbrowser should not be a model dialog but as a part of the app. so we can customize it with a bar in our cordova app to do something with the inappbrowser, I.E. share the link by this plugin: https://github.com/EddyVerbruggen/SocialSharing-PhoneGap-Plugin . But as I searched for the issues, only this issue is related to this. guys, do you mean to have the feature I just mentioned or something else ? ( I am just wondering if I need to open a new feature request ) > A way to control the width/height and x/y placement of the InAppBrowser > UIWebView on the screen > --- > > Key: CB-3397 > URL: https://issues.apache.org/jira/browse/CB-3397 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin InAppBrowser >Affects Versions: 2.7.0 >Reporter: Jan-Dirk Schuitemaker >Assignee: David Kemp >Priority: Minor > Labels: Cordova, InAppBrowser > > Currently the inAppBrowser overlays your app. If you were able to set > position and heigth/width for the InAppBrowser UIWebView you could make it > look as if you are still in the app -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-6667) window.requestFileSystem - callbacks are not fired in a particular circumstance
[ https://issues.apache.org/jira/browse/CB-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127998#comment-14127998 ] Zhang Zengbo commented on CB-6667: -- Hello, as https://issues.apache.org/jira/browse/CB-6761 is marked as resolved but I found it maybe not, could you please see the latest two comments and the attach file of that issue, I don't know how that is related to this issue. > window.requestFileSystem - callbacks are not fired in a particular > circumstance > --- > > Key: CB-6667 > URL: https://issues.apache.org/jira/browse/CB-6667 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File >Affects Versions: 3.4.0 > Environment: Mac OS X 10.9.2 > Android SDK (latest) - API v19 > Eclipse 4.2.2 >Reporter: Kelvin Dart >Priority: Critical > Labels: Android4.4.x, Cordova, androidmanifest.xml, window > > Excuse the essay, but I have a very odd issue that I have singled down to > Cordova which happens in a very specific circumstance on Android. > I have provided a project of the stock Cordova Android project which can be > found here: http://www.filedropper.com/windowfstest - with a minor > modification for the issue I am having. > I have uploaded a compiled APK to install to your device here: > http://www.filedropper.com/windowfstest140509-1404 > Steps to replicate are: > 1) Download and install that APK onto your device (I was using the Samsung > Galaxy S4 with Android 4.4.2 running, no root, and stock TouchWiz ROM, I > *hope* this occurs on other Android devices but have not had an opportunity > to verify). > 2) Start the application and observe an alert appears stating 'dr', then > afterwards another alert appears, 'got FS' - if you check the code, you'll > see this is normal from my app.initialize(). > 3) Once those two alerts have appeared, press the Android 'home' button, to > quit to the main Android home screen. > 4) Go into another app or two and just use your phone normally. What we are > trying to achieve here is for the Android memory management system to > 'end'/kill the WindowFSTest app in the backend. > 5) Go into Apps > WindowFSTest (i.e. the app in question) and hopefully it > will have restarted - the app has to have restarted for the bug to occur, and > observe a few things here: > a) Verify the app has restarted, this can be verified by the 'dr' popup > occuring when Cordova loads. > b) Once you are confident the app has been restarted, observe the initial > 'dr' popup, but *not* the 'got FS' popup - this is the bug, the > window.requestFileSystem does not fire the callbacks for some reason - and I > do not know why. > N.b. there are a few things to note here which is why the bug is tricky to > replicate AND I imagine will be even more difficult to debug at a lower level > ;-) > 1) The Android system has to kill the app in the backend once you've pressed > the 'home' button - there's no way of determining when this has happened, > just use the phone like ordinary for half a minute or so - normally it kills > it after a short period. > 2) The way to restart the app is via Apps > WindowFSTest (not via the task > manager). > 3) ***IMPORTANT*** the above two steps seem to occur only when you run it > from a compiled APK, not directly from source/debug APK - so it's not as easy > to debug since you cannot put line breaks in the Java file(s). > Although not perfect, one way to fix this is to use: > android:launchMode="singleTop" > In AndroidManifest.xml - since it ensures the app is 'resumed' instead of > restarted. > I can provide a video upon request illustrating the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6761) Calling a function the first time no callbacks are being executed
[
https://issues.apache.org/jira/browse/CB-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124939#comment-14124939
]
Zhang Zengbo commented on CB-6761:
--
Hi , I think I am facing the same issue but it seems not fixed even I upgrade
to use 3.6.x dev branch. could somebody confirm this ? please download
attached tarball and extract to an empty dir for test. I test it on a Nexus 5
with 4.4.4, the first time I take the picture, it doesn't show; the second time
I take the picture, even I cancel it, the first picture shows.
> Calling a function the first time no callbacks are being executed
> -
>
> Key: CB-6761
> URL: https://issues.apache.org/jira/browse/CB-6761
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
>Affects Versions: 3.5.0
> Environment: Nexus 5, Android 4.4.2
>Reporter: Roy Ackermann
>Assignee: Andrew Grieve
>Priority: Blocker
> Labels: bridge, callback, function
> Attachments: sidemenu.tar.gz
>
>
> Using different functions the same error occurs. Calling a function the first
> time no callbacks are being executed. There is no error in the log. Using the
> same function again for a second call, everything works fine. Now the first
> call is being executed as well and I receive the callback from the first
> excution.
> It looks like something is wainting. It is odd that the second call works and
> executes the first call as well.
> I found this bug on this calls:
> - window.requestFileSystem(LocalFileSystem.PERSISTENT, 3097152, gotFS, fail);
> - navigator.camera.getPicture(onSuccessCapturePhoto, onFailCamera, {
> targetWidth: 1200, targetHeight: 1200, quality: 55, destinationType:
> Camera.DestinationType.FILE_URI, saveToPhotoAlbum: true,
> correctOrientation:true});
> - navigator.camera.getPicture(onSuccessGetPhoto, onFailCamera, { targetWidth:
> 1000,targetHeight: 1000, quality: 65, destinationType:
> Camera.DestinationType.FILE_URI , saveToPhotoAlbum: false , sourceType:
> Camera.PictureSourceType.SAVEDPHOTOALBUM, correctOrientation:true});
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-6761) Calling a function the first time no callbacks are being executed
[
https://issues.apache.org/jira/browse/CB-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhang Zengbo updated CB-6761:
-
Attachment: sidemenu.tar.gz
reproduce this issue with 3.6.x dev version.
> Calling a function the first time no callbacks are being executed
> -
>
> Key: CB-6761
> URL: https://issues.apache.org/jira/browse/CB-6761
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
>Affects Versions: 3.5.0
> Environment: Nexus 5, Android 4.4.2
>Reporter: Roy Ackermann
>Assignee: Andrew Grieve
>Priority: Blocker
> Labels: bridge, callback, function
> Attachments: sidemenu.tar.gz
>
>
> Using different functions the same error occurs. Calling a function the first
> time no callbacks are being executed. There is no error in the log. Using the
> same function again for a second call, everything works fine. Now the first
> call is being executed as well and I receive the callback from the first
> excution.
> It looks like something is wainting. It is odd that the second call works and
> executes the first call as well.
> I found this bug on this calls:
> - window.requestFileSystem(LocalFileSystem.PERSISTENT, 3097152, gotFS, fail);
> - navigator.camera.getPicture(onSuccessCapturePhoto, onFailCamera, {
> targetWidth: 1200, targetHeight: 1200, quality: 55, destinationType:
> Camera.DestinationType.FILE_URI, saveToPhotoAlbum: true,
> correctOrientation:true});
> - navigator.camera.getPicture(onSuccessGetPhoto, onFailCamera, { targetWidth:
> 1000,targetHeight: 1000, quality: 65, destinationType:
> Camera.DestinationType.FILE_URI , saveToPhotoAlbum: false , sourceType:
> Camera.PictureSourceType.SAVEDPHOTOALBUM, correctOrientation:true});
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
