1. I stumbled over this weird behavior with my UWP-Apps too.
    Did you find some more information about this in the meantime?

    It still happens with the Current SDK (June 2016).

    BTW: The MSDN documentation you are quoting does not document the behavior it only says that e.Exception is not guaranteed to match the Exception originally thrown.

Leave a Reply

Your email address will not be published. Required fields are marked *