Complete
over 4 years ago

WERETECH-6805

This was addressed in CIQ 3.1.1.

How to debug an unhandled exception

On a fresh Eclipse install on macOS High Sierra with recommended settings (several example apps do build and run), I can't seem to get a strack trace after an unhandled exception (aka app crash). Without that information, it's pretty much impossible to debug an app, so I guess I just missed some setting.

What did I miss?
Former Member
Former Member
Parents
  • over 6 years ago
    A nice thing about try/catch is that you can use it to continue running for something that's recoverable in your app. (no pesky IQ! reports from users!) there's just a simple example var val; try { val=Application.Property.getValue("badkey"); } catch(e) { val=defaultValue; } There are cases I use it for the "this is recoverable" aspect. It could also be used for a user input that throws an exception for some reason. Depending on your code, a single try/catch block could stop the IQ! reports. A "bad XYZ" on the screen instead
Comment
  • over 6 years ago
    A nice thing about try/catch is that you can use it to continue running for something that's recoverable in your app. (no pesky IQ! reports from users!) there's just a simple example var val; try { val=Application.Property.getValue("badkey"); } catch(e) { val=defaultValue; } There are cases I use it for the "this is recoverable" aspect. It could also be used for a user input that throws an exception for some reason. Depending on your code, a single try/catch block could stop the IQ! reports. A "bad XYZ" on the screen instead
Children
No Data