[TIMOB-23439] Windows: JS Errors thrown in async callbacks don't show "red screen of death"
GitHub Issue | n/a |
---|---|
Type | Story |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2016-07-08T23:44:51.000+0000 |
Affected Version/s | Release 5.3.0 |
Fix Version/s | Release 6.0.0 |
Components | Windows |
Labels | n/a |
Reporter | Christopher Williams |
Assignee | Kota Iguchi |
Created | 2016-05-25T21:03:39.000+0000 |
Updated | 2016-10-19T15:22:35.000+0000 |
Description
This is a parity issue. When running our mocha suite, we have a number of assertions inside JS callback functions. When an assertion fails on other platforms like iOS/Android, we show a "red screen of death" (on Android, it's more like an "ugly red dialog of death"). On Windows, we don't appear to do the same and the assertion error sort of gets squashed. We end up instead getting timeouts on the tests.
The PR for this ticket also includes some unhandled exception handling to spit out a crash log file, which _may_ be helpful for TIMOB-23411 debugging.
https://github.com/appcelerator/titanium_mobile_windows/pull/721
https://github.com/appcelerator/titanium_mobile_windows/pull/767 This PR contains mostly improvement for internal exception handling & refactoring. We might want to change the ticket type to *Story* as it's difficult to test this from QE side.
Closing based off Kotas comment