[ 
https://issues.apache.org/jira/browse/CB-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Marsh updated CB-13281:
----------------------------
    Attachment: Crash issue.zip

Repro steps:

1. Open this project in iOS 10+
2. Select the top "input" (I recommend using an ios emulator, but a real device 
with a keyboard will do)
3. Start tabbing quickly. You may need to go back to the top one and do it 
several times. (It doesn't cycle back to the top). 
4. Eventually the app will crash. (It took me about 3 go rounds.)

> Cordova crashes with UIPopoverPresentationController exception in web forms
> ---------------------------------------------------------------------------
>
>                 Key: CB-13281
>                 URL: https://issues.apache.org/jira/browse/CB-13281
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-ios
>    Affects Versions: 3.5.0, 3.6.0
>         Environment: iOS 10.3.1, xCode 8.3.3, Cordova 7.0.0
>            Reporter: Nick Marsh
>            Assignee: Shazron Abdullah
>         Attachments: Crash issue.zip
>
>
> This issue is present on iOS 10, with Cordova 7.0
> When tabbing through web forms, if a select dropdown is tabbed over too 
> quickly, the app crashes with the following exception:
> {code}
> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch 
> this in the debugger.
> The methods in the UIConstraintBasedLayoutDebugging category on UIView listed 
> in <UIKit/UIView.h> may also be helpful.
> 2017-09-14 11:23:35.298666-0500 Care At Home[7945:770343] [LayoutConstraints] 
> Unable to simultaneously satisfy constraints.
>       Probably at least one of the constraints in the following list is one 
> you don't want. 
>       Try this: 
>               (1) look at each constraint and try to figure out which you 
> don't expect; 
>               (2) find the code that added the unwanted constraint or 
> constraints and fix it. 
> (
>     "<NSLayoutConstraint:0x60000009be90 
> _UIButtonBarStackView:0x7ff82141b080.width <= 0   (active)>",
>     "<NSLayoutConstraint:0x60000009b710 'UIView-leftMargin-guide-constraint' 
> H:|-(15)-[UILayoutGuide:0x60000019fe40'UIViewLayoutMarginsGuide'](LTR)   
> (active, names: '|':_UIButtonBarStackView:0x7ff82141b080 )>",
>     "<NSLayoutConstraint:0x60000009b7b0 'UIView-rightMargin-guide-constraint' 
> H:[UILayoutGuide:0x60000019fe40'UIViewLayoutMarginsGuide']-(15)-|(LTR)   
> (active, names: '|':_UIButtonBarStackView:0x7ff82141b080 )>"
> )
> Will attempt to recover by breaking constraint 
> <NSLayoutConstraint:0x60000009b7b0 'UIView-rightMargin-guide-constraint' 
> H:[UILayoutGuide:0x60000019fe40'UIViewLayoutMarginsGuide']-(15)-|(LTR)   
> (active, names: '|':_UIButtonBarStackView:0x7ff82141b080 )>
> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch 
> this in the debugger.
> The methods in the UIConstraintBasedLayoutDebugging category on UIView listed 
> in <UIKit/UIView.h> may also be helpful.
> 2017-09-14 11:23:35.358 Care At Home[7945:770343] *** Terminating app due to 
> uncaught exception 'NSRangeException', reason: '-[UITableView 
> _contentOffsetForScrollingToRowAtIndexPath:atScrollPosition:]: row (0) beyond 
> bounds (0) for section (0).'
> *** First throw call stack:
> (
>       0   CoreFoundation                      0x0000000109893b0b 
> __exceptionPreprocess + 171
>       1   libobjc.A.dylib                     0x00000001092cf141 
> objc_exception_throw + 48
>       2   CoreFoundation                      0x00000001098fc625 
> +[NSException raise:format:] + 197
>       3   UIKit                               0x000000010a7f368a 
> -[UITableView _contentOffsetForScrollingToRowAtIndexPath:atScrollPosition:] + 
> 1679
>       4   UIKit                               0x000000010a7f42b9 
> -[UITableView scrollToRowAtIndexPath:atScrollPosition:animated:] + 39
>       5   UIKit                               0x000000010ab5d5f4 
> -[UIWebSelectTableViewController viewWillAppear:] + 150
>       6   UIKit                               0x000000010a847bad 
> -[UIViewController _setViewAppearState:isAnimating:] + 447
>       7   UIKit                               0x000000010a8483c3 
> -[UIViewController __viewWillAppear:] + 147
>       8   UIKit                               0x000000010a81df87 
> __56-[UIPresentationController runTransitionForCurrentState]_block_invoke + 
> 1041
>       9   UIKit                               0x000000010a6ab853 
> _runAfterCACommitDeferredBlocks + 318
>       10  UIKit                               0x000000010a69881c 
> _cleanUpAfterCAFlushAndRunDeferredBlocks + 532
>       11  UIKit                               0x000000010a6ca560 
> _afterCACommitHandler + 137
>       12  CoreFoundation                      0x0000000109839717 
> __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
>       13  CoreFoundation                      0x0000000109839687 
> __CFRunLoopDoObservers + 391
>       14  CoreFoundation                      0x000000010981e720 
> __CFRunLoopRun + 1200
>       15  CoreFoundation                      0x000000010981e016 
> CFRunLoopRunSpecific + 406
>       16  GraphicsServices                    0x000000010e97ca24 
> GSEventRunModal + 62
>       17  UIKit                               0x000000010a69f134 
> UIApplicationMain + 159
>       18  [MY APP]                        0x0000000107871b71 main + 65
>       19  libdyld.dylib                       0x000000010c8d265d start + 1
>       20  ???                                 0x0000000000000001 0x0 + 1
> )
> libc++abi.dylib: terminating with uncaught exception of type NSException
> {code}
> This issue was present in iOS 8, but was said to be resolved. However, it 
> seems to be present again on iOS 10, and I could not find any corresponding 
> bug reports. 
> Please let me know if you need additional information.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to