Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

[Solved] Cloud Diagnostics Hololens Support

Discussion in 'Unity Cloud Diagnostics' started by ferretnt, Apr 23, 2019.

  1. ferretnt

    ferretnt

    Joined:
    Apr 10, 2012
    Posts:
    412
    We have enabled Cloud Diagnostics for a UWP hololens app. We are not seeing any logs from the hololens in the cloud diagnostics "Crashes and Exceptions" page. Crashes and Exceptions from the editor in the same project are logging fine.

    We have tried:

    - Throwing an intentionally unhandled C# exception from a safe place where it won't harm the call stack (the bottom of a Start() function)
    - Explicitly Debug.LogException an exception containing a string with the platform's name.

    The hololens is connected to wifi constanty.

    Can you confirm cloud diagnostics works on UWP?
     
  2. ferretnt

    ferretnt

    Joined:
    Apr 10, 2012
    Posts:
    412
    Anybody?

     
  3. johng_unity

    johng_unity

    Unity Technologies

    Joined:
    Nov 5, 2015
    Posts:
    158
    We are investigating this question and will get back to you. Native crash reports will not get reported but I think unhandled managed exception reports should get reported.
     
  4. ferretnt

    ferretnt

    Joined:
    Apr 10, 2012
    Posts:
    412
    Great - thanks!

    This was tested on Unity 2018.3.10 - all of our projects are at or close to the head of the 2018.x line.

    We were also expecting managed exceptions to work but native not to. That would be in line with AppCentre's capabilities for non-Store builds as UWP won't let you register a global exception handler to catch native crashes.
     
  5. ferretnt

    ferretnt

    Joined:
    Apr 10, 2012
    Posts:
    412
    We submitted a bug report with repro project to help make this clearer. 1149126.
     
  6. johng_unity

    johng_unity

    Unity Technologies

    Joined:
    Nov 5, 2015
    Posts:
    158
    Hi -- just following up on this --- were you able to resolve the issue? I see that your bug was closed.
     
  7. ferretnt

    ferretnt

    Joined:
    Apr 10, 2012
    Posts:
    412
    Yep. Full explanation in an email regarding the bug.

    Thanks for following up.
     
  8. pavel_shchelkun_ilogos

    pavel_shchelkun_ilogos

    Joined:
    Oct 31, 2017
    Posts:
    4
    Has the problem been solved? We are trying the same with UWP (not hololens) builds, but nothing gets tracked in "Crashes and Exceptions" page, not even exceptions thrown in editor play mode.

    We are using Unity 2018.4.0f1.
     
    Last edited: Jul 23, 2019
  9. Ryan-Unity

    Ryan-Unity

    Joined:
    Mar 23, 2016
    Posts:
    1,993
    Hi @pavel_shchelkun_ilogos, the bug mentioned in this thread was closed due to them modifying Application.logMessageReceivedThreaded from a Monobehaviour constructor, which is not supported. Doing that was causing crash reporting to break.

    If you're not seeing your exceptions, even while running in the Editor then this sounds like an unrelated issue. Could you please open a Support ticket from the Cloud Diagnostics tab of the Developer Dashboard of your project so our Support team can help diagnose your issue?
     
  10. pavel_shchelkun_ilogos

    pavel_shchelkun_ilogos

    Joined:
    Oct 31, 2017
    Posts:
    4
    False alarm, it seems to be working fine now. Thanks.
     
    Ryan-Unity likes this.