Releases: getsentry/sentry-unity
Releases · getsentry/sentry-unity
4.0.0-beta.2
Breaking Changes
- Removed Unity 2020 support, which reached End of Life in 2023. Minimum supported version now is 2021. (#2313)
Features
- The SDK now has a dedicated sample scene for third party plugins like Cysharp, or DOTween. (#2289)
- The SDK now automatically marks stack frames from
CysharpandDG.Tweeningas non in-app. This highly improves the resulting stack trace quality in the issues details. (#2285)
Fixes
- The SDK no longer accesses
AnalyticsSessionInfo.userIdwhen targeting console platforms. This was leading to crashes during launch. (#2309) - The SDK now deduplicates trace generation during startup and scene loading (#2301)
- The SDK no longer appends multiple upload tasks when building for Android (#2300)
- Fixed false positive ANR events on
WebGL, i.e. when switching tabs, or unfocusing the player (#2306) - The SDK now automatically picks up previously missing debug symbols - i.e.
BurstDebugInformation, by passing the
target directory path to Sentry CLI. Sentry CLI then automatically and recursively picks up any not yet uploaded symbols. (#2298) - The check used to verify whether the current thread is the main-thread now includes
JobsUtility.IsExecutingJobto support running in Burst. (#2226) - For targeting iOS, the Unity SDK now brings an iOS-only
.xcframework, reducing package size. (#2264)
Dependencies
- Bump .NET SDK from v5.12.0 to v5.15.0 (#2259, #2274, #2291, #2315)
- Bump Cocoa SDK from v8.51.0 to v8.54.0 (#2265)
- Bump Java SDK from v8.17.0 to v8.21.1 (#2261, #2280, #2283, #2299, #2308, #2311)
- Bump Native SDK from v0.9.1 to v0.10.1 (#2275, #2303)
- Bump CLI from v2.50.2 to v2.53.0 (#2276, #2288, #2302)
- Bump Cocoa SDK from v8.54.0 to v8.55.1 (#2305)
4.0.0-beta.1
Fixes
- The SDK now waits for 'End of Frame' before capturing a screenshot. This should address any blank or malformed screenshots previously attached to events. The SDK now also only captures one screenshot for the first error event in each individual frame. (#2240)
Dependencies
4.0.0-beta.0
Breaking Changes
-
Removed Unity 2019 support, which reached End of Life in 2022. Minimum supported version now is 2020. (#2231)
-
Breaking Change: The Unity SDK's static API has been moved from
Sentry.Unity.SentryUnityandSentry.SentrySdktoSentry.Unity.SentrySdk. This change enables manual/programatic SDK initialization with full functionality, previously only available through auto-initialization. The underlying .NET SDK'sSentrySdkclass is now internal, and several previously public classes likeSentryInitializationandSentryIntegrationsare now internal.Migration: Update your
usingdirectives fromusing Sentry;tousing Sentry.Unity;. IDEs like Rider can automatically import the missing references. In some cases, you may need bothusing Sentry.Unity;(for the static API) andusing Sentry;(for types likeSentryId). No changes are required to your actual SDK method calls (e.g.,SentrySdk.CaptureException()remains the same). (#2227, #2239)
Features
- The SDK now comes with a
SentryUserFeedbackprefab ready to be used. You can drag and drop it into your scene or
customize it by creating your own variant. The user feedback feature allows your users to provide feedback in form
of a written message that can optionally have a screenshot attached. Read more about it (here). (#2220)
Dependencies
3.2.3
Significant change in behavior
- The SDK no longer attaches screenshots when capturing errors in the Unity Editor. (#2163)
Fixes
- When targeting Android, the SDK no longer causes
SIGABORTcrashes due toattempting to detach while still running code. (#2215) - The SDK no longer causes crashes with
EXCEPTION_ACCESS_VIOLATION_READwhen using the Mono scripting backend. The SDK now adds the active scene name to the context in IL2CPP builds only (#2206)
Dependencies
3.2.2
Fixes
- When targeting WebGL with an unsupported configuration (i.e. when the exception support is set to
none), the SDK now shows an error at build time instead of a runtime failure (#2141) - When targeting Desktop Platforms, Sentry-CLI now respects the SDK's debug logging verbosity (#2138)
- When targeting iOS, the SDK now correctly updates the Sentry CLI options used for debug symbol upload when appending builds (#2146)
- When targeting iOS and setting
IgnoreCliErrors = true, the Xcode build will now succeed even if the symbol upload itself failed. This is aimed to allow users to unblock themselves (#2136) - Sentry CLI no longer requires the 'Organisation' option, and they have been removed from the configuration window. If you're providing an Organisation right now, nothing changes. Fresh setups will have the option omitted (#2137)
Dependencies
3.2.1
3.2.0
Fixes
- Drastically improved performance of scope sync when targeting Android (#2107)
- When targeting macOS, the SDK no longer fails to sync the scope to native events (#2104)
- Updated the options grouping in the configuration window (#2121)
Features
- The SDK now links errors and events (managed and native errors) via
trace ID. This allows you to correlate events captured from different layers of your game (#1997, #2089, #2106) - The trace used to connect errors on different layers of your game gets regenerated every time the app gains focus, or the active scene changes (#2123)
- The SDK now reports the game's name as part of the app context (2083)
- The SDK now reports the active scene's name as part of the
Unity Context(2084)
Dependencies
- Bump Cocoa SDK from v8.45.0 to v8.49.1 (#2063, #2071, #2105, #2106)
- Bump Java SDK from v8.3.0 to v8.9.0 (#2066, #2075, #2092, #2103, #2111, #2125)
- Bump CLI from v2.42.2 to v2.43.0 (#2065, #2082, #2085)
- Bump .NET SDK from v5.2.0 to v5.6.0 (#2067, #2093, #2102, #2126)
- Bump Native SDK from v0.8.1 to v0.8.4 (#2077, #2087, #2117)
3.1.0
3.0.2
Fixes
- Resolved an issue where the SDK would not properly annotate the ViewHierarchy's
AttachmentType. This would cause it to not render properly on the issues-page on Sentry (#2036) - The SDK now ensures that the correct version of the Android SDK gets used during the build. This prevents dependency conflicts and no longer requires "clean" builds to resolve (#2031)
