I am trying to use Developer Data Diagnostics to see crash reports. I’m using Unity 6.2 with Dev data turned on for my build. I’m building a release build to ios TestFlight. In the diagnostic dashboard I see the user session when I launch the app (yay). I have a timed exception after 20 seconds (throw new System.Exception(“test exception please ignore”)
which crashes the app. This crash does not show up on the dashboard! Why!? I’ve made sure to use my cell network on my device to get around firewalls. Yes, the Unity Project IDs are correct. Where is my crash report?
As an aside the reason I’m even using is this is because I can’t get Firebase crashlytics working on retail ios builds either (Debug works fine).
I’ve sunk a week into this and I still have no crash reports… dying here. Thanks for any help.
While I can’t speak to the specifics of Developer Data Diagnostics, do your logs either in this case or when using Crashlytics show anything abberant when starting the app?
Thank you for taking the time to reply. I have not spent a lot of time debugging Developer Data Diagnostics. In the case of Crashlytics it’s a real head scratcher. I’ve extensively debugged it and there’s nothing obvious that is wrong.
-When I build with Debug everything works. I see the crashes on the Crashlytics dashboard. Everything is good.
-When I build for Release, I get one initial crash reported and then everything after than stops showing up on the dashboard. In the debug logs everything appears to be working correctly with reports being packaged and sent… they just never make it to the dashboard.
-When I make an archive and install from testflight, I don’t have access to the logs, but nothing ever shows up on the dashboard… just nothing.
I’ve done all the obvious stuff:
-Make sure to run the app multiple times.
-Run on cell to bipass firewalls
-Check the Project ID match
-Make sure I’m not incorrectly filtering the reports on the dashboard
I just have no idea why it’s not working. I switched to the Unity solution hoping it would just work… but no… no crash reports either.
Sorry for coming back to this so late but a thought occured to me about why both might fail:
For production apps, Apple can recompile bitcode apps on their end and invalidates local DSYM. You may need to download them from Apple and reupload from there.
This look promising. I will try it and report back. Thanks!
Hey @indoflaven,
I’m unsure if you were able to resolve this, but if you are still having issues, feel free to open a support request from the Dashboard, and a member of our Support Team will gladly take a look at this issue (missing crash reports) with you 
This is the script I use personally when testing Cloud Diagnostics/Engine Diagnostics.
Thank you as well @joefspiro for jumping in and offering suggestions
Kind Regards,
Thank you very much for your reply. The both the Unity cloud crash analytics and Google Crashlytics are now working. To be completely honest, I’m not sure what the problem… I didn’t do anything specific to “fix” it that I’m aware. And I get human readable reports without having to upload my own DSYM (which joefspiro had suggested). The only thing I can guess is that my method of generating test crashes was not being picked up (dispite directly using an example from the google documentation). The exception I have seen correctly reported are real world exceptions and that’s what I care about… so for now I’m good to go.
Thanks again, -Mike