Search Unity

  1. We are migrating the Unity Forums to Unity Discussions. On July 12, the Unity Forums will become read-only. On July 15, Unity Discussions will become read-only until July 18, when the new design and the migrated forum contents will go live. Read our full announcement for more information and let us know if you have any questions.

Question How to build for Windows Store to have meaningful crash/hang debug log?

Discussion in 'Windows' started by FVS, Aug 11, 2022.

  1. FVS

    FVS

    Joined:
    Aug 10, 2015
    Posts:
    58
    My game on Microsoft Store hangs/crashes on some devices, but I can't get any helpful info on the developer dashboard. The failures are referenced as "Unknown", and here is their explanation on "Unknown":
    Failure names that include !unknown mean that symbols weren’t present, so we couldn’t identify the failure name. Be sure to include symbols in your package to get accurate failure analysis. Failure names that include !unknown_error_in_ and !unknown_function mean that we weren’t able to gather complete details for various other reasons.!Unknown failure name indicates that nocabs have been collected for failure.
    So, my question is, is there any build setting in Unity or VS so that I can get some helpful info in the dashboard?
     

    Attached Files:

  2. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,756
    I assume you're already checking this checkbox when creating the application package? upload_2022-8-11_13-39-53.png

    Other than that, I really have no idea. How many downloads do you have? Is 23 crashes a significant portion of your install base?
     
  3. FVS

    FVS

    Joined:
    Aug 10, 2015
    Posts:
    58
    I probably did, I'll make sure it is checked in the next build.
    23 failures, including 4 hangs. It matters to me because MS says they will unpublish the game because of the hangs if I don't submit an update. It just happened before, I submitted an update (without fixing anything), and now it happened again shortly after the update. Guess I'll have to keep doing that if I don't know how to fix it.