Manoel Aranda Neto
Manoel Aranda Neto
this field should also be set to `true` whenever there's a stack trace, eg, segfault etc
> I can't remember why I created this issue. If you, @untitaker, tell me we shouldn't use the field, I'm happy to close the issue. This issue came up after...
> +33,190 > > 🤯 @brustolin please double check the bundle size increase, with this addition, that could be a new problem.
@bruno-garcia ^ user consent request.
@AshStefanOltmann a built-in feature for that makes sense, but we're not there yet, thanks for reporting. there are workarounds tho, you can decide to initialize or not the SDK depending...
@motiz88 is there something that we can help with to move this forward? thanks.
@BYK the release was done via `getsentry/publish`.
> The actual Changelog and the changelog entry in the GitHub releases page are correct. I've fixed them manually, they were wrong and that's the reason I've opened this issue....
@kamilogorek yep, I get that, and we already use `auto` -> https://github.com/getsentry/sentry-react-native/blob/main/.craft.yml#L2 I thought that @BYK meant, not using the `Unreleased` tag at all, since we use `auto` + `Unreleased`...
Maybe I've fixed the changelog file only and not the GH release (because it was correct), not 100% sure now since I've been checking many of the recent releases for...