chore(deps): update Cocoa SDK to v8.49.0 #2105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps modules/sentry-cocoa.properties from 8.48.0 to 8.49.0.
Auto-generated by a dependency updater.
Changelog
8.49.0
Features
Important
With the addition of the new profiling configuation API, the previous profiling API are deprecated and will be removed in the next major version of the SDK:
SentryOptions.enableProfiling
SentryOptions.isProfilingEnabled
SentryOptions.profilesSampleRate
SentryOptions.profilesSampler
SentryOptions.enableLaunchProfiling
Additionally, note that the behavior of
SentrySDK.startProfiler()
will change once the above APIs are removed, as follows: before adding the new configuration API (SentryProfileOptions
),SentrySDK.startProfiler()
would unconditionally start a continuous profile if bothSentryOptions.profilesSampleRate
andSentryOptions.profilesSampler
werenil
, or no-op if either was non-nil
(meaning the SDK would operate under original, transaction-based, profiling model). In the next major version,SentryOptions.profilesSampleRate
andSentryOptions.profilesSampler
will be removed, andSentrySDK.startProfile()
will become a no-op unless you configureSentryProfileOptions.sessionSampleRate
to a value greater than zero (which is its default). If you already have calls toSentrySDK.startProfiler()
in your code, ensure you properly configureSentryProfileOptions
viaSentryOptions.configureProfiling
to avoid losing profiling coverage.Fixes
Improvements