Maybe a bit unrelated, but it popped up last week.
Since 2021.3.27 I get promoted to the bug report screen after a Unity crash, without the old/usual popup to go to the logs or make a report.
I wondered if I should always make a report (if my reproduction is unknown) to get more info to QA, or just one and then ignore the popup in follow-up crashes
Hello DD!
It’s probably safe to just report an issue once, with as much information as you can provide about the steps leading up to that crash, and wait for our QA team to reach out if they require additional information.
Would it be helpful for QA to add an option like ‘send log data only’ option so QA has a bigger sample size for crash issues?
Unreal has something like this I think where you can just send the crash data so their QA can see trends in crashes better
To add, the option to go to the crash logs are also not present in 2021.3.27, since the bug report tool attached files are not clickable
The question is what to do with semi-random crashes, where there are no super clear repro steps (“Unity crashes when I change scenes, it happens like once every hour”), but that maybe the logs have something interesting in them?
The bug reporter seems to urge me to submit something in those cases. Unity devs on here and personally also seem to want me to submit bug reports in those cases.
But if the crashes aren’t super easily reproducible I always get a “can’t repro, closing” reply to my bug report and I feel like an idiot.
So there is some (intentional?) mismatch between what you (meaning Unity, not you personally) communicate to your users with words (which is something along the lines of “please submit a bug report so we can investigate”), and what your systems, processes and policies you have in place communicate with actions (which is something along the lines of “please take that random crash bug report and shove it up your arse”).