locked
Is calling "Application.Current.Exit()" considered as crash in new dashboard reports? RRS feed

  • Question

  • There is a huge difference between the app crash rate of our app in the old Windows Phone Dashboard and the new unified one. On the same day it has 2 crashes in the old and 14 in the new dashboard. I know that the new dashboard is more accurate, because it counts crashes that don't include a crash dump and that it is not the case in the old dashboard.

    In our app we use the method Application.Current.Exit() to exit the app programmaticaly. I know that is not best practices, but the user has to restart the app in some situations due to a WP8.1 platform bug.So for better UX we close the app programmatically for the user.

    The point is that I'd like to know if such a "bad practice exit" of an app may be considered as app crash in the new dashboard and not in the old one. Do we have 14 real crashes or do we have maybe 4 real plus 10 programmatically crashes.

    Thanks for your answers!

    Wednesday, June 17, 2015 11:45 AM

Answers

  • I do not think Application.Current.Exit would show as a crash but it is possible that an exception is created when you call Application.Current.Exit because something does not get a close properly.  What does the crash report say on the dashboard on what happened?  
    Wednesday, June 17, 2015 12:10 PM
  • Hi Karimej,

    I do not think Application.Currnet.Exit would show as a crash as well as Ken. There is no reporting bug window when closing app using Application.Current.Exit method. The other 13 crashes may be related to other issues.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, June 19, 2015 8:35 AM

All replies

  • I do not think Application.Current.Exit would show as a crash but it is possible that an exception is created when you call Application.Current.Exit because something does not get a close properly.  What does the crash report say on the dashboard on what happened?  
    Wednesday, June 17, 2015 12:10 PM
  • On the day I had the 14 crashes I have only one crash with an error associated:

    APPLICATION_HANG_TIMEOUT_c0000194_Windows.UI.Xaml.dll!CXcpDispatcher::Tick

    For the other 13 crashes there is no further information available.

    Wednesday, June 17, 2015 12:36 PM
  • Hi Karimej,

    I do not think Application.Currnet.Exit would show as a crash as well as Ken. There is no reporting bug window when closing app using Application.Current.Exit method. The other 13 crashes may be related to other issues.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, June 19, 2015 8:35 AM
  • Hi Ken and Herro,

    thanks for you thoughts on this. I assume that, too. But I don't know for sure. We will try to fix every bug in the app and see if there are still crashes left.

    Kind regards,
    Karim

    Monday, June 22, 2015 7:41 AM
  • Hi Karim,

    It's a public API to shut down app programmatically though it's not a recommend way. But it is sure this method is not the cause of crash in your new dashboard.

    You are welcome to post here if you have questions.

    I will close this thread if there is no question in this case. Thank you for understanding.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, June 23, 2015 9:50 AM