Hi @main owl. I'm happy to dig into this for you! I'll check my internal sources for answers to your question! :wave:
#sentry-native crash client interface
terse otterBOT
The knowledge sources indicate that the Sentry Native SDK does not, by default, spawn any built‑in UI or “client interface” for end users when a crash or error is captured.
Instead, it works in the background:
- For normal usage, you initialize the SDK and it captures crashes/signals and uploads minidumps or events to Sentry silently. [Native crashes]
- To verify that it’s working during development, you typically trigger a test event (for example, a message event like
"It works!") and then check the Sentry project dashboard in the browser. [Native verify]
If you want a visible interface for users, there are two patterns mentioned:
-
External crash reporter executable
You can configure an external crash reporter (a separate app you build) that Sentry Native launches on crash. That external app can show a UI, collect feedback, etc., and is passed the crash report path as an argument. [External crash reporter] -
Custom user‑feedback flows (feature requests)
There are open/closed feature requests discussing adding hooks likeonCrashedLastRunso that applications can build their own feedback UI and then submit to Sentry’s user‑feedback endpoint, but this is not described as a finished, built‑in UI feature in the Native SDK. [User feedback issue; Crash modal request]
So, out of the box:
- No: Sentry Native does not show a crash dialog or “message sent” popup to the user.
- Yes: You can build and wire up your own UI (for example via an external crash reporter) if you need visible confirmation or feedback collection.