Enhancing Crashlytics Reporting: Timely Delivery of Non-Fatal Reports

## What feature would you like to see?

I've been seeing a ton of important non-fatal reports missing from Crashlytics lately. Turns out, reports only get sent when the app crashes or restarts (please correct me if I'm wrong!). This is a real problem for a couple of reasons:

_User Relaunch Roulette_: We have no control over when users restart the app, so reports could be stuck forever. Asking users to restart just for reports isn't exactly an option either. This means reports are delayed, and by the time we see them, the info might be old news.

_Apps That Never Sleep_: These days, apps can run for ages without needing a restart. Some might even run forever! Relying solely on restarts for reports is clearly not a good approach.

Here's my suggestions:

_Dev Report Control:_ Let developers manually send reports whenever they want. We might not need them instantly, but sending them within seconds or minutes would be a huge improvement.

_Smarter Reporting System:_ We need a smarter way to send reports internally, not just when the app crashes or restarts. Maybe reports could be sent after a certain amount of time has passed or when a specific number of reports have been collected.

## How would you use it?

It depends on your solution, as long as it guarantees timely report delivery to the Crashlytics dashboard

The issue names no files, tests, or entry points. Begin by locating the Crashlytics non-fatal report delivery path and confirming when reports are currently sent; done means an agreed mechanism delivers collected reports to the Crashlytics dashboard without requiring an app crash or restart.

Written by the indexing model from the issue text.