This project is read-only.
1

Closed

Errors getting swallowed internally

description

I seem to be having some problems with exceptions never seeing the light of day. I decided to strip the app down to a basic implementation and still the exceptions seem to disappear.

I've attached a sample application, all it does is:
  • Attaches to the Application UnhandledException event
  • Attaches to the TashScheduler.UnobservedTaskException
  • On navigating to a page it throws an exception (inside of the NavigateTo method to be exact)
Neither of the exception handlers are fired.

Now I'm not sure if this is an Okra problem or something "bigger" but I do know that if I don't use Okra, so basically take the blank project template and throw an exception in OnNavigationTo, the "standard" handler for a navigation event, it does hit the UnhandledException handler I have.

file attachments

Closed Dec 3, 2012 at 10:28 PM by AndyWilkinson
Issue fixed with changeset 93506dc06c41.

comments

AndyWilkinson wrote Sep 4, 2012 at 6:25 PM

Hi,

Thanks for the bug report and the attached solution. I can reproduce this problem and follow the exception out of Okra, but never into the UnhandledException handler. I'll look into it.

Thanks,
 Andy

AndyWilkinson wrote Dec 3, 2012 at 10:27 PM

Sorry to take so long to look into this issue - this seems to be a common problem with async calls. I've updated the Okra source code release with a fix that will catch any exceptions during activation and reinject them into the Application.UnhandledException event handlers.

I've tested your sample project against this build of Okra and this time the event handler is executed. Let me know if you still have problems with this.

Thanks for reporting this,
Andy