Issue
When you report SDK behavior to the Sentry Support team or in one of our repositories, we may ask you for a minimal reproduction to help us investigate.
What is a minimal reproduction application?
A minimal reproduction (sometimes called a minimal reproducible example, or MRE) is the smallest possible collection of source code and data files that reliably triggers the behavior or issue you're seeing.
The key word is minimal: it should contain only what's needed to reproduce the problem. No extra features, no non-essential dependencies, and no private information.
Why it helps
A minimal reproduction gives us precise, self-contained context, which usually speeds up resolution significantly.
IIt often helps you, too: the act of stripping an issue down to its essentials frequently surfaces the root cause (and sometimes the fix) before you even send it to us.
What to include
The SDK and version you're using
The smallest amount of code needed to trigger the behavior
Any configuration or environment details essential to reproduce it (framework, runtime version, etc.)
What to leave out
Unrelated features or business logic
Dependencies that aren't required to trigger the issue
Secrets, production DSNs, tokens, or any private data
Need a starting point?
Stack Overflow's guide to minimal reproducible examples is a great walkthrough of the general approach.