We can perfectly reproduce the error, so long as the debugger is NOT attached.
Any suggestions on trouble shooting?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We can perfectly reproduce the error, so long as the debugger is NOT attached.
Any suggestions on trouble shooting?
ok…
i’ll have to follow up later and build a sample solution to repro this
In a view model, we were exectuting navigation, and then on the next line calling a method that called other methods that included callbacks.
We swithed it so the page we navigated to then called that method.
Before the fix…
The app never crashed when debugging, never throws an error.
With no debugger attached, it failed inconsistentely with the emulator. Interestingly enough, it did NOT ever fail with a Samsung Focus, but did fail 100% of the time on a Samsung Omnia.
By fail I mean it crashes, with no exception available to do anything with…