Releases: getsentry/sentry-java
Releases · getsentry/sentry-java
6.19.0
Features
- Add Screenshot and ViewHierarchy to integrations list (#2698)
- New ANR detection based on ApplicationExitInfo API (#2697)
- This implementation completely replaces the old one (based on a watchdog) on devices running Android 11 and above:
- New implementation provides more precise ANR events/ANR rate detection as well as system thread dump information. The new implementation reports ANRs exactly as Google Play Console, without producing false positives or missing important background ANR events.
- New implementation reports ANR events with a new mechanism
mechanism:AppExitInfo
. - However, despite producing many false positives, the old implementation is capable of better enriching ANR errors (which is not available with the new implementation), for example:
- Capturing screenshots at the time of ANR event;
- Capturing transactions and profiling data corresponding to the ANR event;
- Auxiliary information (such as current memory load) at the time of ANR event.
- If you would like us to provide support for the old approach working alongside the new one on Android 11 and above (e.g. for raising events for slow code on main thread), consider upvoting this discussion.
- The old watchdog implementation will continue working for older API versions (Android < 11)
- The old implementation reports ANR events with the existing mechanism
mechanism:ANR
- The old implementation reports ANR events with the existing mechanism
- This implementation completely replaces the old one (based on a watchdog) on devices running Android 11 and above:
- Open up
TransactionOptions
,ITransaction
andIHub
methods allowing consumers modify start/end timestamp of transactions and spans (#2701) - Send source bundle IDs to Sentry to enable source context (#2663)
- For more information on how to enable source context, please refer to #633
Fixes
- Android Profiler on calling thread (#2691)
- Use
configureScope
instead ofwithScope
inHub.close()
. This ensures that the main scope releases the in-memory data when closing a hub instance. (#2688) - Remove null keys/values before creating concurrent hashmap in order to avoid NPE (#2708)
- Exclude SentryOptions from R8/ProGuard obfuscation (#2699)
- This fixes AGP 8.+ incompatibility, where full R8 mode is enforced
Dependencies
6.18.1
6.18.0
Features
- Attach Trace Context when an ANR is detected (ANRv1) (#2583)
- Make log4j2 integration compatible with log4j 3.0 (#2634)
- Instead of relying on package scanning, we now use an annotation processor to generate
Log4j2Plugins.dat
- Instead of relying on package scanning, we now use an annotation processor to generate
- Create
User
andBreadcrumb
from map (#2614) - Add
sent_at
to envelope header item (#2638)
Fixes
- Fix timestamp intervals of PerformanceCollectionData in profiles (#2648)
- Fix timestamps of PerformanceCollectionData in profiles (#2632)
- Fix missing propagateMinConstraints flag for SentryTraced (#2637)
- Fix potential SecurityException thrown by ConnectivityManager on Android 11 (#2653)
- Fix aar artifacts publishing for Maven (#2641)
Dependencies
6.17.0
Features
- Add
name
andgeo
toUser
(#2556) - Add breadcrumbs on network changes (#2608)
- Add time-to-initial-display and time-to-full-display measurements to Activity transactions (#2611)
- Read integration list written by sentry gradle plugin from manifest (#2598)
- Add Logcat adapter (#2620)
- Provide CPU count/frequency data as device context (#2622)
Fixes
- Trim time-to-full-display span if reportFullyDisplayed API is never called (#2631)
- Fix Automatic UI transactions having wrong durations (#2623)
- Fix wrong default environment in Session (#2610)
- Pass through unknown sentry baggage keys into SentryEnvelopeHeader (#2618)
- Fix missing null check when removing lifecycle observer (#2625)
Dependencies
6.16.0
Features
- Improve versatility of exception resolver component for Spring with more flexible API for consumers. (#2577)
- Automatic performance instrumentation for WebFlux (#2597)
- You can enable it by adding
sentry.enable-tracing=true
to yourapplication.properties
- You can enable it by adding
- The Spring Boot integration can now be configured to add the
SentryAppender
to specific loggers instead of theROOT
logger (#2173)- You can specify the loggers using
"sentry.logging.loggers[0]=foo.bar
and"sentry.logging.loggers[1]=baz
in yourapplication.properties
- You can specify the loggers using
- Add capabilities to track Jetpack Compose composition/rendering time (#2507)
- Adapt span op and description for graphql to fit spec (#2607)
Fixes
- Fix timestamps of slow and frozen frames for profiles (#2584)
- Deprecate reportFullDisplayed in favor of reportFullyDisplayed (#2585)
- Add mechanism for logging integrations and update spring mechanism types (#2595)
- NOTE: If you're using these mechanism types (
HandlerExceptionResolver
,SentryWebExceptionHandler
) in your dashboards please update them to use the new types.
- NOTE: If you're using these mechanism types (
- Filter out session cookies sent by Spring and Spring Boot integrations (#2593)
- We filter out some common cookies like JSESSIONID
- We also read the value from
server.servlet.session.cookie.name
and filter it out
- No longer send event / transaction to Sentry if
beforeSend
/beforeSendTransaction
throws (#2591) - Add version to sentryClientName used in auth header (#2596)
- Keep integration names from being obfuscated (#2599)
- Change log level from INFO to WARN for error message indicating a failed Log4j2 Sentry.init (#2606)
- The log message was often not visible as our docs suggest a minimum log level of WARN
- Fix session tracking on Android (#2609)
- Incorrect number of session has been sent. In addition, some of the sessions were not properly ended, messing up Session Health Metrics.
Dependencies
6.16.0-beta.1
6.15.0
Features
- Adjust time-to-full-display span if reportFullDisplayed is called too early (#2550)
- Add
enableTracing
option (#2530)- This change is backwards compatible. The default is
null
meaning existing behaviour remains unchanged (setting eithertracesSampleRate
ortracesSampler
enables performance). - If set to
true
, performance is enabled, even if notracesSampleRate
ortracesSampler
have been configured. - If set to
false
performance is disabled, regardless oftracesSampleRate
andtracesSampler
options.
- This change is backwards compatible. The default is
- Detect dependencies by listing MANIFEST.MF files at runtime (#2538)
- Report integrations in use, report packages in use more consistently (#2179)
- Implement
ThreadLocalAccessor
for propagating Sentry hub with reactor / WebFlux (#2570)- Requires
io.micrometer:context-propagation:1.0.2+
as well as Spring Boot 3.0.3+ - Enable the feature by setting
sentry.reactive.thread-local-accessor-enabled=true
- This is still considered experimental. Once we have enough feedback we may turn this on by default.
- Checkout the sample here: https://github.com/getsentry/sentry-java/tree/main/sentry-samples/sentry-samples-spring-boot-webflux-jakarta
- A new hub is now cloned from the main hub for every request
- Requires
Fixes
- Leave
inApp
flag for stack frames undecided in SDK if unsure and let ingestion decide instead (#2547) - Allow
0.0
error sample rate (#2573) - Fix memory leak in WebFlux related to an ever growing stack (#2580)
- Use the same hub in WebFlux exception handler as we do in WebFilter (#2566)
- Switch upstream Jetpack Compose dependencies to
compileOnly
insentry-compose-android
(#2578)- NOTE: If you're using Compose Navigation/User Interaction integrations, make sure to have the following dependencies on the classpath as we do not bring them in transitively anymore:
androidx.navigation:navigation-compose:
androidx.compose.runtime:runtime:
androidx.compose.ui:ui:
- NOTE: If you're using Compose Navigation/User Interaction integrations, make sure to have the following dependencies on the classpath as we do not bring them in transitively anymore:
6.14.0
6.13.1
6.13.0
Features
- Send cpu usage percentage in profile payload (#2469)
- Send transaction memory stats in profile payload (#2447)
- Add cpu usage collection (#2462)
- Improve ANR implementation: (#2475)
- Add
abnormal_mechanism
to sessions for ANR rate calculation - Always attach thread dump to ANR events
- Distinguish between foreground and background ANRs
- Add
- Improve possible date precision to 10 μs (#2451)
Fixes
- Fix performance collector setup called in main thread (#2499)
- Expand guard against CVE-2018-9492 "Privilege Escalation via Content Provider" (#2482)
- Prevent OOM by disabling TransactionPerformanceCollector for now (#2498)