Android agent release notesRSS

Bug Fixes

• Fixed an issue where stack traces for Unity errors were not displayed correctly.
• Fixed an issue that prevented summary metrics from being recorded when the app returned to the foreground after its initial launch.
• Fixed an issue where invalid JSON in log entries could cause errors.

Support statement

We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.

Fix

• Added support for 16KB page size

Support statement

• The Android NDK agent version 1.1.1 and above requires Android agent 7.5.1 and higher.
• The Android NDK agent version 1.1.0 and above requires Android agent 7.5.0 and higher.
• The Android NDK agent version 1.0.3 and above requires Android agent 6.11.0 and higher.
• Versions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower.

We recommend you to upgrade the agent regularly, at least every 3 months.

Bug Fixes

• Improved performance to resolve ANRs when reporting logs
• Fixed an issue to continue reporting logs upon termination of the application
• Resolved an issue with application state monitoring and data transmission
• Improved few violations when turning on strictmode

Support statement

We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.

Bug Fixes

• Addressed an issue with custom interaction conflicts with default interaction

Support statement

We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.

Bug Fixes

• Addressed a problem where the agent failed to parse double values with non-zero digits after the decimal point.
• Corrected an issue where the agent recorded app launch metrics as astronomical values.
• Fixed build issues related to newer versions of Dexguard.

Support statement

We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.

New

• Upgrade agent to support AGP 8.8
• Added processId as a session attribute for application exit info to ensure better troubleshooting ability

Bug Fixes

• Resolved an issue that logs are not sent after first app launch
• Resolved the issue where HttpHeaders were not being tracked when added through an interceptor.

Support statement

We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.

New Features

• Introduced build-time feature flag for LogInstrumentation.
• Enhanced logging by including Session Attributes as Log Attributes.

Bug Fixes

• Resolved missed session events in the background reporting feature.
• Fixed memory leak related to mobile handled exceptions during network unavailability.
• Corrected application crash scenario during agent shutdown.

Support statement

We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.

New features

• Implemented OpenTelemetry (Otel) Distributed Tracing.
• Added support for Gzip compression for log data ingestion.
• Included Application Not Responding (ANR) thread data in the reporting process.

Fixed issues

• Fixed an issue with log instrumentation that caused build failures.
• Fixed an issue where throwable errors generated repetitive entries in Logcat.
• Fixed a crash caused by calling removeAttributes before starting an agent.
• Fixed user-reported issues with log functionality.

Support statement

We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.

New

• Adds support for the Android Gradle Plugin 8.7.

Fixed issues

• Resolved an issue where ProGuard/DexGuard mapping files weren't being properly uploaded to New Relic, improving crash reporting accuracy.
• Fixed a crash that occurred when Kotlin mutable maps were passed to breadcrumbs and custom events.
• Corrected behavior where default interactions were being recorded even when the feature flag was disabled.

Support statement

We recommend updating the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy.