Dhiogo Brustolin
Dhiogo Brustolin
Hello @marcelofabri, are you testing this during debug? If so, [we removed local symbolication](https://github.com/getsentry/sentry-cocoa/blob/main/CHANGELOG.md#890) to reduce in device processing. You can enable this by setting `options.debug = true` don't forget...
> Note that calling SentrySDK.start(options: options) makes it work again. I didn't get this, were you not calling `SentrySDK.start` before? This is required for the SDK to work.
Interesting. I don't know a reason for symbolication not work when you don't start SentrySDK, we would need to investigate this. PS: You can get SentryClient from SentryHub if you...
What will happen when we release the new version? Will Changelog have an empty `unreleased` section? This I don't like.
This will be fixed with this [PR](https://github.com/getsentry/sentry-cocoa/pull/3651)
Hello @diogot, most likely until Thursday.
This can happen (and will be fixed) if you're trying to use SentrySDK from a background thread before starting it. Can you confirm this scenario @diogot?
> Should I leave this ticket open? Yes. We still need to fix this.
Hello @JacobKingDev. Can you confirm if it's possible that you're trying to use the SDK before calling `SentrySDK.start`?
Thanks @JacobKingDev for the reply. This is a new case, we will need to investigate. Maybe it is related to the rest of the issue.