Releases: bugsnag/bugsnag-android-performance
Releases · bugsnag/bugsnag-android-performance
v1.14.0
Changes
- Introduced
RemoteSpanContext to allow cross-layer parenting of spans, along with easy encoding of traceparent headers
#378
Bug fixes
- Corrected the naming of the aggregate CPU metrics attributes
#380
v1.13.0
Changes
- Optionally capture and report CPU and Memory use on selected spans (opt-in using
PerformanceConfiguration.enabledMetrics)
#366
v1.12.0
Changes
- Added LoadingIndicator composable as a way to easily extend ViewLoad end times to interactivity
#336
- Added LoadingIndicatorView as a way for xml layouts to easily extend ViewLoad end times to interactivity
#352
v1.11.0
Changes
- Added mechanism for delivering external spans with natively-captured metrics (for initial use with React Native rendering metrics)
#327
v1.10.1
Bug fixes
- Move remaining I/O to the worker thread in
BugsnagPerformance.start - avoiding StrictMode violations
#310
v1.10.0
Bug fixes
- Untagged socket violation when StrictMode is enabled #297
#306
- Fixed issue where background apps didn't consistently flush the current batch of spans
#305
Enhancements
- Formally introduced the
bugsnag-android-performance-compose module and MeasuredComposable to report the performance of Composables
#299
v1.9.1
Bug fixes
- Fixed Warm AppStarts being over reported due to app-backgrounding not being fully reported internally
#299
- Custom spans are reported with a "bugsnag.span.category" to match behaviour in our other SDKs
#300
v1.9.0
Changes
- Slow & Frozen frame metrics can optionally be reported (
PerformanceConfiguration.autoInstrumentRendering)
#290
v1.8.0
Changes
- Attribute limits can now be configured in the
AndroidManifest.xml
#284
v1.7.0
Bug fixes
Changes
- Use API key subdomain as default Performance endpoint.
#277
- Trace Propagation URLs and service name can be configured in
AndroidManifest.xml
#281
- Added configurable limit to number of span attributes per span.
#280
