Search Unity

Trouble setting up Cloud Diagnostics to report crashes

Discussion in 'Unity Cloud Diagnostics' started by LGGDevs, Aug 22, 2019.

  1. LGGDevs

    LGGDevs

    Joined:
    Dec 1, 2016
    Posts:
    3
    I've been trying to set up Cloud Diagnostics to automatically send us crash details when they happen.
    Added the service to the Unity project and enabled Cloud Diagnostics there and in the dashboard, and added a force crash button just to test.
    Regardless of whether I'm in editor or in a build however, nothing is ever reported. Haven't gotten it to work a single time.

    The project is using Unity 2017.4.17f1 with a personal license. The forced crash is just using Application.ForceCrash(0).

    Any help here?
     
  2. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,168
    Hi @LGGDevs, you're not doing anything wrong. Cloud Diagnostics seems to be having an issue with receiving native crash reports at the moment. We'll be looking into this right away, however our dev is out on vacation until next week so it may take some time to get to. Exception reporting is unaffected, though, so using methods like Debug.LogException() will still work. We'll update here when there's more info.
     
  3. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,168
    Hi @LGGDevs, were you by any chance developing on a Mac? Cloud Diagnostics actually doesn't support native crashes in the Mac Editor. The Mac Player is supported and both Windows Editor and Player native crashes are logged, but we are still working on adding support for the Mac Editor.