[jira] [Created] (CB-5430) [plugin-network-information] JS getInfo method does not work on Android
Pepe Cano created CB-5430:
-
Summary: [plugin-network-information] JS getInfo method does not
work on Android
Key: CB-5430
URL: https://issues.apache.org/jira/browse/CB-5430
Project: Apache Cordova
Issue Type: Bug
Components: Android
Reporter: Pepe Cano
The error is described at http://stackoverflow.com/a/19894873/446317
Current JS implementation originates and exception because the "getInfo" method
is available at the "navigator.connection" variable.
So, the only way to use the API is to call directly:
cordovaRef.exec(function(v) {
}, function() {
}, "NetworkStatus", "getConnectionInfo", []);
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5429) cordova-plugin-network-information fails on iOS when updateReachability is executed
Pepe Cano created CB-5429: - Summary: cordova-plugin-network-information fails on iOS when updateReachability is executed Key: CB-5429 URL: https://issues.apache.org/jira/browse/CB-5429 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.1.0 Reporter: Pepe Cano The use case is: - app has not any active network connection - put the "app" in background and access to WIFI settings to active any WIFI connection - "updateReachability" is executed and the [self sendPluginResult] call originates and EXC_BAD_ACCESS exception on the _callbackId variable. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Issue Comment Deleted] (CB-3027) getCurrentPosition timeout does not work and it blocks application execution
[
https://issues.apache.org/jira/browse/CB-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pepe Cano updated CB-3027:
--
Comment: was deleted
(was: [~shazron], I think the problem comes because the setTimeout and [self
startLocation:enableHighAccuracy] are executed before hidding the splashscreen
with navigator.splashscreen.hide(). In this case, the timeout callback is never
executed.
May you confirm that this could be an issue?
In my case, calling navigator.geolocation.getCurrentPosition after a period of
splashscreen hide, the getCurrentPosition works.)
> getCurrentPosition timeout does not work and it blocks application execution
>
>
> Key: CB-3027
> URL: https://issues.apache.org/jira/browse/CB-3027
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 2.5.0, 2.6.0
> Environment:
>Reporter: Pepe Cano
>Assignee: Shazron Abdullah
>Priority: Critical
> Fix For: 2.8.0
>
>
> I have experienced this problem with cordova 2.5 & 2.6 in iOS 6.1.3, iPhone 4.
> Timeout param is not working, so I decided to implement the same behavior
> with timing-function, however _getCurrentPosition_ seems to be executed
> synchronously instead of asynchronously, and because _timeout_ does not work,
> neither locationTimeout function or error callback are executed and the
> application is blocked waiting for getCurrentPosition response.
> {code}
> var positionError = function() {
>/// do something on error
> };
> var locationTimeout = window.setTimeout(function() {
> // work-around to solve timeout error
> positionError();
> }, 1000);
> navigator.geolocation.getCurrentPosition( function(response) {
> clearTimeout(locationTimeout);
> positionNext(response);
> }, function(error) {
> clearTimeout(locationTimeout);
> positionError();
> }, { maximumAge: 3000, timeout: 1000 });
> {code}
> Could I misunderstand any internal functionality?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-3027) getCurrentPosition timeout does not work and it blocks application execution
[
https://issues.apache.org/jira/browse/CB-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660706#comment-13660706
]
Pepe Cano edited comment on CB-3027 at 5/17/13 2:12 PM:
[~shazron], I think the problem comes because the setTimeout and [self
startLocation:enableHighAccuracy] are executed before hidding the splashscreen
with navigator.splashscreen.hide(). In this case, the timeout callback is never
executed.
May you confirm that this could be an issue?
In my case, calling navigator.geolocation.getCurrentPosition after a period of
splashscreen hide, the getCurrentPosition works.
was (Author: ppcano):
[~shazron], I think the problem comes because the setTimeout and [self
startLocation:enableHighAccuracy] are executed before hidding the splashscreen
with navigator.splashscreen.hide(). In this case, the timeout callback is never
executed.
May you confirm that this could be an issue?
In my case, calling navigator.geolocation.getCurrentPosition after hide the
splashscreen works without any issue.
> getCurrentPosition timeout does not work and it blocks application execution
>
>
> Key: CB-3027
> URL: https://issues.apache.org/jira/browse/CB-3027
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 2.5.0, 2.6.0
> Environment:
>Reporter: Pepe Cano
>Assignee: Shazron Abdullah
>Priority: Critical
> Fix For: 2.8.0
>
>
> I have experienced this problem with cordova 2.5 & 2.6 in iOS 6.1.3, iPhone 4.
> Timeout param is not working, so I decided to implement the same behavior
> with timing-function, however _getCurrentPosition_ seems to be executed
> synchronously instead of asynchronously, and because _timeout_ does not work,
> neither locationTimeout function or error callback are executed and the
> application is blocked waiting for getCurrentPosition response.
> {code}
> var positionError = function() {
>/// do something on error
> };
> var locationTimeout = window.setTimeout(function() {
> // work-around to solve timeout error
> positionError();
> }, 1000);
> navigator.geolocation.getCurrentPosition( function(response) {
> clearTimeout(locationTimeout);
> positionNext(response);
> }, function(error) {
> clearTimeout(locationTimeout);
> positionError();
> }, { maximumAge: 3000, timeout: 1000 });
> {code}
> Could I misunderstand any internal functionality?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-3027) getCurrentPosition timeout does not work and it blocks application execution
[
https://issues.apache.org/jira/browse/CB-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660706#comment-13660706
]
Pepe Cano edited comment on CB-3027 at 5/17/13 1:33 PM:
[~shazron], I think the problem comes because the setTimeout and [self
startLocation:enableHighAccuracy] are executed before hidding the splashscreen
with navigator.splashscreen.hide(). In this case, the timeout callback is never
executed.
May you confirm that this could be an issue?
In my case, calling navigator.geolocation.getCurrentPosition after hide the
splashscreen works without any issue.
was (Author: ppcano):
[~shazron], I think the problem comes because the setTimeout and [self
startLocation:enableHighAccuracy] are executed before hidding the splashscreen
with navigator.splashscreen.hide()
May you confirm that this could be an issue?
In my case, calling navigator.geolocation.getCurrentPosition after hide the
splashscreen works without any issue.
> getCurrentPosition timeout does not work and it blocks application execution
>
>
> Key: CB-3027
> URL: https://issues.apache.org/jira/browse/CB-3027
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 2.5.0, 2.6.0
> Environment:
>Reporter: Pepe Cano
>Assignee: Shazron Abdullah
>Priority: Critical
> Fix For: 2.8.0
>
>
> I have experienced this problem with cordova 2.5 & 2.6 in iOS 6.1.3, iPhone 4.
> Timeout param is not working, so I decided to implement the same behavior
> with timing-function, however _getCurrentPosition_ seems to be executed
> synchronously instead of asynchronously, and because _timeout_ does not work,
> neither locationTimeout function or error callback are executed and the
> application is blocked waiting for getCurrentPosition response.
> {code}
> var positionError = function() {
>/// do something on error
> };
> var locationTimeout = window.setTimeout(function() {
> // work-around to solve timeout error
> positionError();
> }, 1000);
> navigator.geolocation.getCurrentPosition( function(response) {
> clearTimeout(locationTimeout);
> positionNext(response);
> }, function(error) {
> clearTimeout(locationTimeout);
> positionError();
> }, { maximumAge: 3000, timeout: 1000 });
> {code}
> Could I misunderstand any internal functionality?
--
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-3027) getCurrentPosition timeout does not work and it blocks application execution
[
https://issues.apache.org/jira/browse/CB-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660706#comment-13660706
]
Pepe Cano commented on CB-3027:
---
[~shazron], I think the problem comes because the setTimeout and [self
startLocation:enableHighAccuracy] are executed before hidding the splashscreen
with navigator.splashscreen.hide()
May you confirm that this could be an issue?
In my case, calling navigator.geolocation.getCurrentPosition after hide the
splashscreen works without any issue.
> getCurrentPosition timeout does not work and it blocks application execution
>
>
> Key: CB-3027
> URL: https://issues.apache.org/jira/browse/CB-3027
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 2.5.0, 2.6.0
> Environment:
>Reporter: Pepe Cano
>Assignee: Shazron Abdullah
>Priority: Critical
> Fix For: 2.8.0
>
>
> I have experienced this problem with cordova 2.5 & 2.6 in iOS 6.1.3, iPhone 4.
> Timeout param is not working, so I decided to implement the same behavior
> with timing-function, however _getCurrentPosition_ seems to be executed
> synchronously instead of asynchronously, and because _timeout_ does not work,
> neither locationTimeout function or error callback are executed and the
> application is blocked waiting for getCurrentPosition response.
> {code}
> var positionError = function() {
>/// do something on error
> };
> var locationTimeout = window.setTimeout(function() {
> // work-around to solve timeout error
> positionError();
> }, 1000);
> navigator.geolocation.getCurrentPosition( function(response) {
> clearTimeout(locationTimeout);
> positionNext(response);
> }, function(error) {
> clearTimeout(locationTimeout);
> positionError();
> }, { maximumAge: 3000, timeout: 1000 });
> {code}
> Could I misunderstand any internal functionality?
--
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-3027) getCurrentPosition timeout does not work and it blocks application execution
[
https://issues.apache.org/jira/browse/CB-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649069#comment-13649069
]
Pepe Cano commented on CB-3027:
---
[~shazron], any update?
> getCurrentPosition timeout does not work and it blocks application execution
>
>
> Key: CB-3027
> URL: https://issues.apache.org/jira/browse/CB-3027
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 2.5.0, 2.6.0
> Environment:
>Reporter: Pepe Cano
>Assignee: Shazron Abdullah
>Priority: Critical
> Fix For: 2.7.0
>
>
> I have experienced this problem with cordova 2.5 & 2.6 in iOS 6.1.3, iPhone 4.
> Timeout param is not working, so I decided to implement the same behavior
> with timing-function, however _getCurrentPosition_ seems to be executed
> synchronously instead of asynchronously, and because _timeout_ does not work,
> neither locationTimeout function or error callback are executed and the
> application is blocked waiting for getCurrentPosition response.
> {code}
> var positionError = function() {
>/// do something on error
> };
> var locationTimeout = window.setTimeout(function() {
> // work-around to solve timeout error
> positionError();
> }, 1000);
> navigator.geolocation.getCurrentPosition( function(response) {
> clearTimeout(locationTimeout);
> positionNext(response);
> }, function(error) {
> clearTimeout(locationTimeout);
> positionError();
> }, { maximumAge: 3000, timeout: 1000 });
> {code}
> Could I misunderstand any internal functionality?
--
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-3027) getCurrentPosition timeout does not work and it blocks application execution
[
https://issues.apache.org/jira/browse/CB-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641886#comment-13641886
]
Pepe Cano commented on CB-3027:
---
[~shazron], the problem does not happen in the first APP run, but in the
following runs.
Have you tried this case?
I am still testing with the APP using Cordova 2.6.
> getCurrentPosition timeout does not work and it blocks application execution
>
>
> Key: CB-3027
> URL: https://issues.apache.org/jira/browse/CB-3027
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 2.5.0, 2.6.0
> Environment:
>Reporter: Pepe Cano
>Assignee: Shazron Abdullah
>Priority: Critical
> Fix For: 2.7.0
>
>
> I have experienced this problem with cordova 2.5 & 2.6 in iOS 6.1.3, iPhone 4.
> Timeout param is not working, so I decided to implement the same behavior
> with timing-function, however _getCurrentPosition_ seems to be executed
> synchronously instead of asynchronously, and because _timeout_ does not work,
> neither locationTimeout function or error callback are executed and the
> application is blocked waiting for getCurrentPosition response.
> {code}
> var positionError = function() {
>/// do something on error
> };
> var locationTimeout = window.setTimeout(function() {
> // work-around to solve timeout error
> positionError();
> }, 1000);
> navigator.geolocation.getCurrentPosition( function(response) {
> clearTimeout(locationTimeout);
> positionNext(response);
> }, function(error) {
> clearTimeout(locationTimeout);
> positionError();
> }, { maximumAge: 3000, timeout: 1000 });
> {code}
> Could I misunderstand any internal functionality?
--
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-3027) getCurrentPosition timeout does not work and it blocks application execution
[
https://issues.apache.org/jira/browse/CB-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pepe Cano reopened CB-3027:
---
Reopening issue to check the use case.
> getCurrentPosition timeout does not work and it blocks application execution
>
>
> Key: CB-3027
> URL: https://issues.apache.org/jira/browse/CB-3027
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 2.5.0, 2.6.0
> Environment:
>Reporter: Pepe Cano
>Assignee: Shazron Abdullah
>Priority: Critical
> Fix For: 2.7.0
>
>
> I have experienced this problem with cordova 2.5 & 2.6 in iOS 6.1.3, iPhone 4.
> Timeout param is not working, so I decided to implement the same behavior
> with timing-function, however _getCurrentPosition_ seems to be executed
> synchronously instead of asynchronously, and because _timeout_ does not work,
> neither locationTimeout function or error callback are executed and the
> application is blocked waiting for getCurrentPosition response.
> {code}
> var positionError = function() {
>/// do something on error
> };
> var locationTimeout = window.setTimeout(function() {
> // work-around to solve timeout error
> positionError();
> }, 1000);
> navigator.geolocation.getCurrentPosition( function(response) {
> clearTimeout(locationTimeout);
> positionNext(response);
> }, function(error) {
> clearTimeout(locationTimeout);
> positionError();
> }, { maximumAge: 3000, timeout: 1000 });
> {code}
> Could I misunderstand any internal functionality?
--
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-3027) getCurrentPosition timeout does not work and it blocks application execution
Pepe Cano created CB-3027: - Summary: getCurrentPosition timeout does not work and it blocks application execution Key: CB-3027 URL: https://issues.apache.org/jira/browse/CB-3027 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 2.5.0, 2.6.0 Environment: Reporter: Pepe Cano Assignee: Shazron Abdullah Priority: Critical The description of the issue was reported: https://github.com/shazron/phonegap-questions/issues/10 -- 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-2851) iOS UIKit Crash webView:didCreateOrUpdateScrollingLayer:withContentsLayer
[
https://issues.apache.org/jira/browse/CB-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625437#comment-13625437
]
Pepe Cano commented on CB-2851:
---
It is likely an apple bug, due to a Z-index rendered div.
I have modified the HTML content and the error seems to be disappeared.
> iOS UIKit Crash webView:didCreateOrUpdateScrollingLayer:withContentsLayer
> -
>
> Key: CB-2851
> URL: https://issues.apache.org/jira/browse/CB-2851
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: Xcode 4.6 & 4.6.1 with cordova-ios 2.5 and master
>Reporter: Pepe Cano
>Priority: Minor
> Fix For: Master
>
>
> There are different crashes which appears sometimes on my application startup.
> - [__NSCFDictionary removeFromSuperlayer]
> - EXC_BAD_ACCESS
> The usual two root causes in my opinion are a memory management error (e.g.
> something has died and you've kept an invalid pointer to it because reference
> counting failed) or a not properly initialised thing of some kind that's
> being referenced before it's ready or erroneously, maybe due to a programming
> error.
> Looking at the main thread there I think it's probably something running in
> something like dispatch_async(dispatch_get_main_thread(),^{ ... and the thing
> being run is accessing a pointer that's not valid or (in some cases) points
> to an old, dead thing.
> -> EXC_BAD_ACCESS
> com.apple.main-thread Crashed
> 0 libobjc.A.dylib objc_msgSend + 15
> 1 QuartzCore CALayerGetSuperlayer + 88
> 2 UIKit -[UIView(Hierarchy) superview] + 48
> 3 UIKit __UIViewWillBeRemovedFromSuperview + 94
> 4 UIKit -[UIView(Hierarchy) removeFromSuperview] + 56
> 5 UIKit -[UIScrollView setShowsVerticalScrollIndicator:] + 74
> 6 UIKit -[UIWebDocumentView
> webView:didCreateOrUpdateScrollingLayer:withContentsLayer:scrollSize:forNode:allowHorizontalScrollbar:allowVerticalScrollbar:]
> + 342
> 7 CoreFoundation __invoking___ + 68
> 8 CoreFoundation -[NSInvocation invoke] + 290
> 9 CoreFoundation -[NSInvocation invokeWithTarget:] + 50
> 10 WebKit -[_WebSafeForwarder forwardInvocation:] + 374
> 11 ... libdispatch.dylib _dispatch_call_block_and_release + 10
> 12 libdispatch.dylib _dispatch_client_callout + 22
> 13 libdispatch.dylib _dispatch_main_queue_callback_4CF + 228
> 14 CoreFoundation __CFRunLoopRun + 1288
> 15 CoreFoundation CFRunLoopRunSpecific + 356
> 16 CoreFoundation CFRunLoopRunInMode + 104
> 17 GraphicsServicesGSEventRunModal + 74
> ---
> 0 libobjc.A.dylib objc_msgSend + 15
> 1 UIKit -[UIScrollView(Static)
> _adjustScrollerIndicators:alwaysShowingThem:] + 1938
> 2 UIKit -[UIScrollView _endPanWithEvent:] + 5526
> 3 UIKit -[UIScrollView _gestureRecognizerFailed:] + 334
> 4 UIKit -[UIGestureRecognizer _updateGestureWithEvent:] + 2344
> 5 UIKit ___UIGestureRecognizerUpdate_block_invoke_0543 + 46
> 6 UIKit _UIGestureRecognizerRemoveObjectsFromArrayAndApplyBlocks + 218
> 7 UIKit _UIGestureRecognizerUpdate + 1164
> 8 UIKit -[UIWindow _sendGesturesForEvent:] + 766
> 9 UIKit -[UIWindow sendEvent:] + 90
> 10 UIKit -[UIApplication sendEvent:] + 380
> 11 UIKit _UIApplicationHandleEvent + 6198
> 12 GraphicsServices_PurpleEventCallback + 590
> 13 GraphicsServicesPurpleEventCallback + 34
> 14 ... CoreFoundation
> __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
> 20 UIKit UIApplicationMain + 1120
> 21 Yoin
> ---
> I have also reported to Apple but I did not still know which could be the
> root of the problem.
--
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] [Closed] (CB-2851) iOS UIKit Crash webView:didCreateOrUpdateScrollingLayer:withContentsLayer
[
https://issues.apache.org/jira/browse/CB-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pepe Cano closed CB-2851.
-
Resolution: Not A Problem
It is likely an apple bug, due to a Z-index rendered div.
I have modified the HTML content and the error seems to be disappeared.
> iOS UIKit Crash webView:didCreateOrUpdateScrollingLayer:withContentsLayer
> -
>
> Key: CB-2851
> URL: https://issues.apache.org/jira/browse/CB-2851
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: Xcode 4.6 & 4.6.1 with cordova-ios 2.5 and master
>Reporter: Pepe Cano
>Priority: Minor
> Fix For: Master
>
>
> There are different crashes which appears sometimes on my application startup.
> - [__NSCFDictionary removeFromSuperlayer]
> - EXC_BAD_ACCESS
> The usual two root causes in my opinion are a memory management error (e.g.
> something has died and you've kept an invalid pointer to it because reference
> counting failed) or a not properly initialised thing of some kind that's
> being referenced before it's ready or erroneously, maybe due to a programming
> error.
> Looking at the main thread there I think it's probably something running in
> something like dispatch_async(dispatch_get_main_thread(),^{ ... and the thing
> being run is accessing a pointer that's not valid or (in some cases) points
> to an old, dead thing.
> -> EXC_BAD_ACCESS
> com.apple.main-thread Crashed
> 0 libobjc.A.dylib objc_msgSend + 15
> 1 QuartzCore CALayerGetSuperlayer + 88
> 2 UIKit -[UIView(Hierarchy) superview] + 48
> 3 UIKit __UIViewWillBeRemovedFromSuperview + 94
> 4 UIKit -[UIView(Hierarchy) removeFromSuperview] + 56
> 5 UIKit -[UIScrollView setShowsVerticalScrollIndicator:] + 74
> 6 UIKit -[UIWebDocumentView
> webView:didCreateOrUpdateScrollingLayer:withContentsLayer:scrollSize:forNode:allowHorizontalScrollbar:allowVerticalScrollbar:]
> + 342
> 7 CoreFoundation __invoking___ + 68
> 8 CoreFoundation -[NSInvocation invoke] + 290
> 9 CoreFoundation -[NSInvocation invokeWithTarget:] + 50
> 10 WebKit -[_WebSafeForwarder forwardInvocation:] + 374
> 11 ... libdispatch.dylib _dispatch_call_block_and_release + 10
> 12 libdispatch.dylib _dispatch_client_callout + 22
> 13 libdispatch.dylib _dispatch_main_queue_callback_4CF + 228
> 14 CoreFoundation __CFRunLoopRun + 1288
> 15 CoreFoundation CFRunLoopRunSpecific + 356
> 16 CoreFoundation CFRunLoopRunInMode + 104
> 17 GraphicsServicesGSEventRunModal + 74
> ---
> 0 libobjc.A.dylib objc_msgSend + 15
> 1 UIKit -[UIScrollView(Static)
> _adjustScrollerIndicators:alwaysShowingThem:] + 1938
> 2 UIKit -[UIScrollView _endPanWithEvent:] + 5526
> 3 UIKit -[UIScrollView _gestureRecognizerFailed:] + 334
> 4 UIKit -[UIGestureRecognizer _updateGestureWithEvent:] + 2344
> 5 UIKit ___UIGestureRecognizerUpdate_block_invoke_0543 + 46
> 6 UIKit _UIGestureRecognizerRemoveObjectsFromArrayAndApplyBlocks + 218
> 7 UIKit _UIGestureRecognizerUpdate + 1164
> 8 UIKit -[UIWindow _sendGesturesForEvent:] + 766
> 9 UIKit -[UIWindow sendEvent:] + 90
> 10 UIKit -[UIApplication sendEvent:] + 380
> 11 UIKit _UIApplicationHandleEvent + 6198
> 12 GraphicsServices_PurpleEventCallback + 590
> 13 GraphicsServicesPurpleEventCallback + 34
> 14 ... CoreFoundation
> __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
> 20 UIKit UIApplicationMain + 1120
> 21 Yoin
> ---
> I have also reported to Apple but I did not still know which could be the
> root of the problem.
--
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-2851) iOS UIKit Crash webView:didCreateOrUpdateScrollingLayer:withContentsLayer
[
https://issues.apache.org/jira/browse/CB-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pepe Cano updated CB-2851:
--
Component/s: iOS
Fix Version/s: Master
Description:
There are different crashes which appears sometimes on my application startup.
- [__NSCFDictionary removeFromSuperlayer]
- EXC_BAD_ACCESS
The usual two root causes in my opinion are a memory management error (e.g.
something has died and you've kept an invalid pointer to it because reference
counting failed) or a not properly initialised thing of some kind that's being
referenced before it's ready or erroneously, maybe due to a programming error.
Looking at the main thread there I think it's probably something running in
something like dispatch_async(dispatch_get_main_thread(),^{ ... and the thing
being run is accessing a pointer that's not valid or (in some cases) points to
an old, dead thing.
-> EXC_BAD_ACCESS
com.apple.main-thread Crashed
0libobjc.A.dylib objc_msgSend + 15
1QuartzCore CALayerGetSuperlayer + 88
2UIKit -[UIView(Hierarchy) superview] + 48
3UIKit __UIViewWillBeRemovedFromSuperview + 94
4UIKit -[UIView(Hierarchy) removeFromSuperview] + 56
5UIKit -[UIScrollView setShowsVerticalScrollIndicator:] + 74
6UIKit -[UIWebDocumentView
webView:didCreateOrUpdateScrollingLayer:withContentsLayer:scrollSize:forNode:allowHorizontalScrollbar:allowVerticalScrollbar:]
+ 342
7CoreFoundation __invoking___ + 68
8CoreFoundation -[NSInvocation invoke] + 290
9CoreFoundation -[NSInvocation invokeWithTarget:] + 50
10 WebKit -[_WebSafeForwarder forwardInvocation:] + 374
11 ... libdispatch.dylib _dispatch_call_block_and_release + 10
12 libdispatch.dylib _dispatch_client_callout + 22
13 libdispatch.dylib _dispatch_main_queue_callback_4CF + 228
14 CoreFoundation __CFRunLoopRun + 1288
15 CoreFoundation CFRunLoopRunSpecific + 356
16 CoreFoundation CFRunLoopRunInMode + 104
17 GraphicsServicesGSEventRunModal + 74
---
0libobjc.A.dylib objc_msgSend + 15
1UIKit -[UIScrollView(Static)
_adjustScrollerIndicators:alwaysShowingThem:] + 1938
2UIKit -[UIScrollView _endPanWithEvent:] + 5526
3UIKit -[UIScrollView _gestureRecognizerFailed:] + 334
4UIKit -[UIGestureRecognizer _updateGestureWithEvent:] + 2344
5UIKit ___UIGestureRecognizerUpdate_block_invoke_0543 + 46
6UIKit _UIGestureRecognizerRemoveObjectsFromArrayAndApplyBlocks + 218
7UIKit _UIGestureRecognizerUpdate + 1164
8UIKit -[UIWindow _sendGesturesForEvent:] + 766
9UIKit -[UIWindow sendEvent:] + 90
10 UIKit -[UIApplication sendEvent:] + 380
11 UIKit _UIApplicationHandleEvent + 6198
12 GraphicsServices_PurpleEventCallback + 590
13 GraphicsServicesPurpleEventCallback + 34
14 ... CoreFoundation
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
20 UIKit UIApplicationMain + 1120
21 Yoin
---
I have also reported to Apple but I did not still know which could be the root
of the problem.
was:
There are different crashes which appears sometimes on my application startup.
- [__NSCFDictionary removeFromSuperlayer]
- EXC_BAD_ACCESS
The usual two root causes in my opinion are a memory management error (e.g.
something has died and you've kept an invalid pointer to it because reference
counting failed) or a not properly initialised thing of some kind that's being
referenced before it's ready or erroneously, maybe due to a programming error.
Looking at the main thread there I think it's probably something running in
something like dispatch_async(dispatch_get_main_thread(),^{ ... and the thing
being run is accessing a pointer that's not valid or (in some cases) points to
an old, dead thing.
The errors have disappeared when:
- Removing (FileTransfer/CDVContacts plugin)
- Disabling scrolling in the webView
((UIScrollView*)[self.webView scrollView]).scrollEnabled = NO;
-> EXC_BAD_ACCESS
com.apple.main-thread Crashed
0libobjc.A.dylib objc_msgSend + 15
1QuartzCore CALayerGetSuperlayer + 88
2UIKit -[UIView(Hierarchy) superview] + 48
3UIKit __UIViewWillBeRemovedFromSuperview + 94
4UIKit -[UIView(Hierarchy) removeFromSuperview] + 56
5UIKit -[UIScrollView setShowsVerticalScrollIndicator:] + 74
6UIKit -[UIWebDocumentView
webView:didCreateOrUpdateScrollingLayer:withContentsLayer:scrollSize:forNode:allowHorizontalScrollbar:allowVerticalScrollbar:]
+ 342
7CoreFoundation __invoking___ + 68
8CoreFoundation -[NSInvocation invoke] + 290
9CoreFoundation -
[jira] [Created] (CB-2851) iOS UIKit Crash webView:didCreateOrUpdateScrollingLayer:withContentsLayer
Pepe Cano created CB-2851:
-
Summary: iOS UIKit Crash
webView:didCreateOrUpdateScrollingLayer:withContentsLayer
Key: CB-2851
URL: https://issues.apache.org/jira/browse/CB-2851
Project: Apache Cordova
Issue Type: Bug
Affects Versions: 2.5.0
Environment: Xcode 4.6 & 4.6.1 with cordova-ios (2.5)
Reporter: Pepe Cano
Priority: Minor
There are different crashes which appears sometimes on my application startup.
- [__NSCFDictionary removeFromSuperlayer]
- EXC_BAD_ACCESS
The usual two root causes in my opinion are a memory management error (e.g.
something has died and you've kept an invalid pointer to it because reference
counting failed) or a not properly initialised thing of some kind that's being
referenced before it's ready or erroneously, maybe due to a programming error.
Looking at the main thread there I think it's probably something running in
something like dispatch_async(dispatch_get_main_thread(),^{ ... and the thing
being run is accessing a pointer that's not valid or (in some cases) points to
an old, dead thing.
The errors have disappeared when:
- Removing (FileTransfer/CDVContacts plugin)
- Disabling scrolling in the webView
((UIScrollView*)[self.webView scrollView]).scrollEnabled = NO;
-> EXC_BAD_ACCESS
com.apple.main-thread Crashed
0libobjc.A.dylib objc_msgSend + 15
1QuartzCore CALayerGetSuperlayer + 88
2UIKit -[UIView(Hierarchy) superview] + 48
3UIKit __UIViewWillBeRemovedFromSuperview + 94
4UIKit -[UIView(Hierarchy) removeFromSuperview] + 56
5UIKit -[UIScrollView setShowsVerticalScrollIndicator:] + 74
6UIKit -[UIWebDocumentView
webView:didCreateOrUpdateScrollingLayer:withContentsLayer:scrollSize:forNode:allowHorizontalScrollbar:allowVerticalScrollbar:]
+ 342
7CoreFoundation __invoking___ + 68
8CoreFoundation -[NSInvocation invoke] + 290
9CoreFoundation -[NSInvocation invokeWithTarget:] + 50
10 WebKit -[_WebSafeForwarder forwardInvocation:] + 374
11 ... libdispatch.dylib _dispatch_call_block_and_release + 10
12 libdispatch.dylib _dispatch_client_callout + 22
13 libdispatch.dylib _dispatch_main_queue_callback_4CF + 228
14 CoreFoundation __CFRunLoopRun + 1288
15 CoreFoundation CFRunLoopRunSpecific + 356
16 CoreFoundation CFRunLoopRunInMode + 104
17 GraphicsServicesGSEventRunModal + 74
---
0libobjc.A.dylib objc_msgSend + 15
1UIKit -[UIScrollView(Static)
_adjustScrollerIndicators:alwaysShowingThem:] + 1938
2UIKit -[UIScrollView _endPanWithEvent:] + 5526
3UIKit -[UIScrollView _gestureRecognizerFailed:] + 334
4UIKit -[UIGestureRecognizer _updateGestureWithEvent:] + 2344
5UIKit ___UIGestureRecognizerUpdate_block_invoke_0543 + 46
6UIKit _UIGestureRecognizerRemoveObjectsFromArrayAndApplyBlocks + 218
7UIKit _UIGestureRecognizerUpdate + 1164
8UIKit -[UIWindow _sendGesturesForEvent:] + 766
9UIKit -[UIWindow sendEvent:] + 90
10 UIKit -[UIApplication sendEvent:] + 380
11 UIKit _UIApplicationHandleEvent + 6198
12 GraphicsServices_PurpleEventCallback + 590
13 GraphicsServicesPurpleEventCallback + 34
14 ... CoreFoundation
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
20 UIKit UIApplicationMain + 1120
21 Yoin
---
I have also reported to Apple but I did not still know which could be the root
of the problem.
--
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
