This. It's hard to take app development that doesn't use any kind of crash reporting seriously, tbqh.
Like, there's a crash reported by a user. That's already rare in itself, and average report quality from non technical users varies from nearly useless to misleading. What are you gonna do, ask them where it happened and what they were doing, to guess where in your related code something went wrong?
I would gladly report all the bugs myself manually, with all the details, specifics and reproduction steps. The only problem is 85% of bugs I ever reported either got "won't fix" status (mostly in free software) or just been silently forgotten (mostly at work) or got a "pay first, then ask for fixes" response (when it was about shareware). So I lost enthusiasm. Free software bug reporting also often has a problem of requiring registration in a separate BugZilla for every project but this problem has mostly been resolved by the majority moving to GitHub.
By the way, although I don't want to participate in involuntary and non-transparent automatic error reporting, I find your response logically beautiful. "One step away" - a perfect and reasonable description for this.
You wouldn't though. Because a lot of different crashes (not to mention warnings) are handled automatically and are restarted before you even notice.
If you have android, just connect it to pc, open logcat and filter for errors only. There are still messages every couple seccond. You would get frustrated even if those were simply showed to You as a user, not to mention actively going out of your way to report them
Like, there's a crash reported by a user. That's already rare in itself, and average report quality from non technical users varies from nearly useless to misleading. What are you gonna do, ask them where it happened and what they were doing, to guess where in your related code something went wrong?