Changes for major version 9

[armcknight]

Let's discuss the breaking changes we'd like to see that are waiting on the next major version, à la #877 and #1094

[armcknight]

Integration installation. Per #2941, we dynamically construct integrations based on a list of strings representing their class names. This technically allows for customers to inject their own custom integration classes. It's not clear if this should be supported, how it would work, or what benefit customers can gain from doing so.

The dynamic strategy also discards type safety. We should not do so for the sake of our own convenience. We should figure out a way to do this with a simple API that doesn't rely on stringly typed logic. It should be enough for the boolean properties already present on SentryOptions to control which integrations are enabled or disabled. From there we can have a static code sector that sets things up. No need for looping through strings, using NSClassFromString etc. SentryOptions.integrations should no be a publicly exposed property at all.

[armcknight]

Rename SentryMechanismMeta to something else different than Meta. See #2888 for discussion.

[armcknight]

Found a @todo headerdoc comment stating that SentryDebugImageProvider should be renamed to SentryDebugImage:

sentry-cocoa/Sources/Sentry/Public/SentryDebugImageProvider.h

Line 30 in 98713e6

* @todo This class should be renamed to @c SentryDebugImage in a future version.

[armcknight]

Remove obsoleted public methods in SentryDebugImageProvider deprecated in #3042.

[armcknight]

Update IPHONEOS_DEPLOYMENT_TARGET from 11 to 13. A lot of tooling and dependencies seem to be on iOS 13 now. We only test as far back as 13.7 in CI:

sentry-cocoa/.github/workflows/test.yml

Line 92 in 3de9971

test-destination-os: "13.7"

as that's what's supported in GitHub actions: https://github.com/actions/runner-images/blob/91e422a825d3941ea357a13a91b13d4f4fdc326d/images/macos/macos-11-Readme.md?plain=1#L272

[armcknight]

Similar to macOS versions. IMO whenever we release a major version, it should only support the versions that can actually be tested on CI.

[armcknight]

Make sampleRate / tracesSampleRate / profilesSampleRate / SentryTracesSamplerCallback nonnull: #3529 (comment)

[brustolin]

If we don't need nullability we should stop using NSNumber

[armcknight]

Remove the deprecated SentryOptions.enableProfiling

[armcknight]

Remove the deprecated SentryUser.segment (#4092)

[armcknight]

Change SentrySDK.configureScope from being a block-based API to just returning a scope. Making it a block confers no benefit and makes callsites more complicated because even thought it's not asynchronous, the compiler still enforces capture semantics.

[armcknight]

Remove the public access to SentryHub.scope. The scope should only be accessible by customers via configureScope and it should come with a warning not to retain the provided instance outside the block.

SentryHub.scope has a property getter override that contains a @synchronized critical sector. This detail is unnecessarily hidden from callsites that call e.g. SentrySDK.currentHub.scope. The property should either be called synchronizedScope or the critical sector should be placed inside a method with a similar name.

If it is imperative to protect the thread safety of the property, we should extract it into its own objc interface that keeps the instance private and only exposes a method to access it in a synchronized way.

This would make all callsites that use the scope that require waiting on a lock more obvious that that is what is happening.