Releases: getsentry/sentry-java
Releases · getsentry/sentry-java
8.14.0
Fixes
- Fix Session Replay masking for newer versions of Jetpack Compose (1.8+) (#4485)
Features
- Add New User Feedback Widget (#4450)
- This widget is a custom button that can be used to show the user feedback form
- Add New User Feedback form (#4384)
- We now introduce SentryUserFeedbackDialog, which extends AlertDialog, inheriting the show() and cancel() methods, among others.
To use it, just instantiate it and call show() on the instance (Sentry must be previously initialized).
For customization options, please check the User Feedback documentation.import io.sentry.android.core.SentryUserFeedbackDialog; new SentryUserFeedbackDialog.Builder(context).create().show();
import io.sentry.android.core.SentryUserFeedbackDialog SentryUserFeedbackDialog.Builder(context).create().show()
- We now introduce SentryUserFeedbackDialog, which extends AlertDialog, inheriting the show() and cancel() methods, among others.
- Add
user.id
,user.name
anduser.email
to log attributes (#4486) - User
name
attribute has been deprecated, please useusername
instead (#4486) - Add device (
device.brand
,device.model
anddevice.family
) and OS (os.name
andos.version
) attributes to logs (#4493) - Serialize
preContext
andpostContext
inSentryStackFrame
(#4482)
Internal
- User Feedback now uses SentryUser.username instead of SentryUser.name (#4494)
8.13.3
Fixes
- Send UI Profiling app start chunk when it finishes (#4423)
- Republish Javadoc #4457
- Finalize
OkHttpEvent
even if no active span inSentryOkHttpInterceptor
#4469 - Session Replay: Do not capture current replay for cached events from the past (#4474)
- Session Replay: Correctly capture Dialogs and non full-sized windows (#4354)
- Session Replay: Fix inconsistent
segment_id
(#4471) - Session Replay: Fix crash on devices with the Unisoc/Spreadtrum T606 chipset (#4477)
8.13.2
8.13.1
8.13.0
Warning
Android: Please do not use this version if you're initializing the SDK manually on a background thread, as this could lead to a crash during SDK init (issue details here). We recommend using SDK version 8.13.1 or higher instead.
Features
- Add debug mode for Session Replay masking (#4357)
- Use
Sentry.replay().enableDebugMaskingOverlay()
to overlay the screen with the Session Replay masks. - The masks will be invalidated at most once per
frameRate
(default 1 fps).
- Use
- Extend Logs API to allow passing in
attributes
(#4402)Sentry.logger.log
now takes aSentryLogParameters
- Use
SentryLogParameters.create(SentryAttributes.of(...))
to pass attributes- Attribute values may be of type
string
,boolean
,integer
ordouble
. - Other types will be converted to
string
. Currently we simply calltoString()
but we might offer more in the future. - You may manually flatten complex types into multiple separate attributes of simple types.
- e.g. intead of
SentryAttribute.named("point", Point(10, 20))
you may store it asSentryAttribute.integerAttribute("point.x", point.x)
andSentryAttribute.integerAttribute("point.y", point.y)
- e.g. intead of
SentryAttribute.named()
will automatically infer the type or fall back tostring
.SentryAttribute.booleanAttribute()
takes aBoolean
valueSentryAttribute.integerAttribute()
takes aInteger
valueSentryAttribute.doubleAttribute()
takes aDouble
valueSentryAttribute.stringAttribute()
takes aString
value
- Attribute values may be of type
- We opted for handling parameters via
SentryLogParameters
to avoid creating tons of overloads that are ambiguous.
Fixes
- Isolation scope is now forked in
OtelSentrySpanProcessor
instead ofOtelSentryPropagator
(#4434)- Since propagator may never be invoked we moved the location where isolation scope is forked.
- Not invoking
OtelSentryPropagator.extract
or having asentry-trace
header that failed to parse would cause isolation scope not to be forked. - This in turn caused data to bleed between scopes, e.g. from one request into another
Dependencies
- Bump Spring Boot to
3.5.0
(#4111)
8.12.0
Warning
Android: Please do not use this version if you're initializing the SDK manually on a background thread, as this could lead to a crash during SDK init (issue details here). We recommend using SDK version 8.13.1 or higher instead.
Features
- Add new User Feedback API (#4286)
- We now introduced Sentry.captureFeedback, which supersedes Sentry.captureUserFeedback
- Add Sentry Log Feature (#4372)
- The feature is disabled by default and needs to be enabled by:
options.getLogs().setEnabled(true)
inSentry.init
/SentryAndroid.init
<meta-data android:name="io.sentry.logs.enabled" android:value="true" />
inAndroidManifest.xml
logs.enabled=true
insentry.properties
sentry.logs.enabled=true
inapplication.properties
sentry.logs.enabled: true
inapplication.yml
- Logs can be captured using
Sentry.logger().info()
and similar methods. - Logs also take a format string and arguments which we then send through
String.format
. - Please use
options.getLogs().setBeforeSend()
to filter outgoing logs
- The feature is disabled by default and needs to be enabled by:
Fixes
- Hook User Interaction integration into running Activity in case of deferred SDK init (#4337)
Dependencies
8.11.1 (Stable)
Fixes
- Fix Android profile chunk envelope type for UI Profiling (#4366)
8.11.0
Features
- Make
RequestDetailsResolver
public (#4326)RequestDetailsResolver
is now public and has an additional constructor, making it easier to use a customTransportFactory
Fixes
8.11.0-alpha.1
Features
- Support
globalHubMode
for OpenTelemetry (#4349)- Sentry now adds OpenTelemetry spans without a parent to the last known unfinished root span (transaction)
- Previously those spans would end up in Sentry as separate transactions
- Spans created via Sentry API are preferred over those created through OpenTelemetry API or auto instrumentation
- New option
ignoreStandaloneClientSpans
that prevents Sentry from creating transactions for OpenTelemetry spans with kindCLIENT
(#4349)- Defaults to
false
meaning standalone OpenTelemetry spans with kindCLIENT
will be turned into Sentry transactions
- Defaults to
- Make
RequestDetailsResolver
public (#4326)RequestDetailsResolver
is now public and has an additional constructor, making it easier to use a customTransportFactory
Fixes
8.10.0
Features
- Wrap configured OpenTelemetry
ContextStorageProvider
if available (#4359)- This is only relevant if you see
java.lang.IllegalStateException: Found multiple ContextStorageProvider. Set the io.opentelemetry.context.ContextStorageProvider property to the fully qualified class name of the provider to use. Falling back to default ContextStorage. Found providers: ...
- Set
-Dio.opentelemetry.context.contextStorageProvider=io.sentry.opentelemetry.SentryContextStorageProvider
on yourjava
command - Sentry will then wrap the other
ContextStorageProvider
that has been configured by loading it through SPI - If no other
ContextStorageProvider
is available or there are problems loading it, we fall back to usingSentryOtelThreadLocalStorage
- This is only relevant if you see
Fixes
- Update profile chunk rate limit and client report (#4353)