chore(deps): update Cocoa SDK to v7.30.2 #1123
Closed
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 flutter/scripts/update-cocoa.sh from 7.30.1 to 7.30.2.
Auto-generated by a dependency updater.
Changelog
7.30.2
Fixes
7.30.0
Features
Fixes
7.29.0
Features
Fixes
7.28.0
Features
Fixes
Performance Improvements
7.27.1
Fixes
7.27.0
Features
Fixes
7.26.0
Features
Fixes
component
name source for SentryPerformanceTracker (#2168)7.25.1
Performance Improvements
7.25.0
Features
Fixes
options[sdk][name]
shouldn't clear version (#2139)7.24.1
Fixes
7.24.0
Features
enableCrashHandler
and deprecatedintegrations
(#2049)Fixes
environment
set fromSentryOptions
orconfigureScope
with profiling data (#2095)7.24.0-beta.0
Features
enableCrashHandler
and deprecatedintegrations
(#2049)Fixes
environment
set fromSentryOptions
orconfigureScope
with profiling data (#2095)7.23.0
Features
Fixes
7.22.0
Features
Fixes
7.21.0
Features
Fixes
network_error
(#1957)sdkInfo
(#1960)7.20.0
Features
7.19.0
Features
Fixes
7.18.1
Fixes
7.18.0
Features
Fixes
7.17.0
Features
Fixes
7.16.1
Fixes
7.16.0
Features
Fixes
7.15.0
Features
Fixes
7.14.0
7.13.0
If you are using self-hosted Sentry, this version requires Sentry version >= 21.9.0
to work or you have to manually disable sending client reports via the
sendClientReports
option.7.12.0
Important notice
This release contains a fix for the sampling of transactions. The SDK applied both sample rates for events and transactions when capturing transactions. Previously, when setting sampleRate to 0.0, the SDK would discard all transactions.
This is fixed now by ignoring the sampleRate for transactions. If you use custom values for sampleRate and traceSampleRate or traceSampler, this change will have an impact on you.
If you are using profiling and self-hosted Sentry, this version requires Sentry version >= 22.3.0.
Various fixes & improvements
7.12.0-beta.0
Various fixes & improvements
7.11.0
7.10.2
7.10.1
7.10.0
7.9.0
7.8.0
7.7.0
7.6.1
7.6.0
7.5.4
7.5.3
7.5.2
Various fixes & improvements
7.5.1
7.5.0
7.4.8
7.4.7
7.4.6
7.4.5
7.4.4
7.4.3
7.4.2
7.4.1
7.4.0
7.3.0
7.3.0-beta.0
fix: maxBreadcrumb zero crashes when adding (#1326)
feat: Add tracestate HTTP header support (#1291)
7.2.10
7.2.9
7.2.8
7.2.7
7.2.6
7.2.5
7.2.4
7.2.3
7.2.2
7.2.1
This release fixes a crucial issue for auto performance instrumentation that caused crashes when using nested ViewControllers.
7.2.0
This release contains support for auto performance instrumentation
for ViewControllers, HTTP requests, app start and slow and frozen frames.
Auto Performance Features
More Features
Fixes
Package.swift
(#1169)Performance Improvements
7.2.0-beta.9
7.2.0-beta.8
7.2.0-beta.7
7.2.0-beta.6
7.2.0-beta.5
7.2.0-beta.4
7.2.0-beta.3
7.2.0-beta.2
Package.swift
(#1169)7.2.0-beta.1
7.2.0-beta.0
7.1.4
7.1.3
7.1.2
7.1.1
7.1.0
7.0.3
7.0.2
7.0.1
ref: Prefix TracesSampler with Sentry (#1091)
7.0.0
This is a major bump with the Performance Monitoring API and Out of Memory Tracking, many improvements and a few breaking changes.
For a detailed explanation how to upgrade please checkout the migration guide.
Breaking Changes
Features
Fixes
SentryOptions.sampleRate
that is not >= 0.0 and <= 1.0 the SDK sets it to the default of 1.0.7.0.0-beta.1
Features and Fixes
SentryOptions.sampleRate
that is not >= 0.0 and <= 1.0 the SDK sets it to the default of 1.0.7.0.0-beta.0
7.0.0-alpha.5
Breaking Changes
SentryMechanism.meta
with new classSentryMechanismMeta
. MovedSenryNSError
toSentryMechanismMeta
.Features and Fixes
dispatch_async
and related APIs. #9987.0.0-alpha.4
Breaking Changes
SentryException.thread
withSentryException.threadId
andSentryException.stacktrace
.SentryHub.scope
instead.SentryClient.storeEnvelope
, which is reserved for Hybrid SDKs.SentrySDK.currentHub
andSentrySDK.setCurrentHub
. In case you need this methods, please open up an issue.SentryOptions.maxCacheItems
.Features and Fixes
7.0.0-alpha.3
7.0.0-alpha.2
Features
Breaking Changes
7.0.0-alpha.1
Features and fixes:
Breaking Changes
7.0.0-alpha.0
Breaking Change: This version introduces a change to the grouping of issues. The SDK now sets the
inApp
flag for frames originating from only the main executable using CFBundleExecutable.
In previous versions, all frames originating from the application bundle were marked as
inApp
. This had thedownside of marking frames of private frameworks inside the bundle as
inApp
. This problem is fixed now.Applications using static frameworks shouldn't be affected by this change.
For more information on marking frames as inApp docs.
6.2.1
6.2.0
With this version, Sentry groups errors by domain and code. MyDomain 1 and MyDomain 2
are going to be two separate issues in Sentry. If you are using self-hosted Sentry,
it requires Sentry version >= v21.2.0 to work. Staying on Sentry < v21.2.0 and upgrading
to this version of the SDK won't do any damage. Sentry will group like in previous
versions, but you will see a new group because we slightly changed the wording. If you
are using sentry.io no action is needed. In case you are not satisfied with this change,
you can take a look at
SDK fingerprinting
to group by domain only.
6.1.4
6.1.3
6.1.2
6.1.1
6.1.0
6.1.0-alpha.1
6.1.0-alpha.0
6.0.12
6.0.11
6.0.10
6.0.9
6.0.8
6.0.7
6.0.6
6.0.5
6.0.4
6.0.3
6.0.2
captureEnvelope
on the client #7846.0.1
6.0.0
This is a major bump with lots of internal improvements and a few breaking changes.
For a detailed explanation how to updgrade please checkout the migration guide.
Breaking changes:
Features and fixes: