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
removeAttributesbefore 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.
New features
- Upgrade JDK support to JAVA22.
- Upgrade AGP support to 8.6.
- Add feature flag for event persistence. You can read our docs to learn how to enable this feature].
Fixed issues
- Fixed a corner case to prevent a mismatch between
appbuildidandappversion. - Fixed issue where crashes aren't ingested due to empty
stacktraceElements. - Fixed a
NullValuePointerexception when a shutdown is called. - Fixed a parameter mismatch in the gradle plugin which caused confusion in the logs.
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.
This release is invalid and should not be used.
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.
Fix
- Tighten the logic around metric clearance to prevent dropping metrics when harvest is unsuccessful
- Add
sessionIdattribute as part of the log reporting
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.
Fix
- Tighten implementation logic to better handle potential memory leakage, and add more logging for debugging visibilities.
Support statement
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.
New
- Add mobile log reporting feature. You can read our docs to learn more and how to enable this feature.
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.
New
- Reduce the overall size of the agent.
- Extend
AgentNDK.Builder.withANRMonitor(boolean)to disable native ANR detection as well.
Support statement
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.
New
- Add
ApplicationExitInfoas part of data reporting, and the feature is enabled by default. To disable go to your mobile applications entity application settings page.
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.
New
- Add
ApplicationExitInfoas part of data reporting. - Add the ability to report data while an application goes into a background state. You can read our docs to learn how to enable this feature.
- Includes code for upcoming log forwarding feature. See your Account Team for information about early adoption.
Fix
- Enhance
setUserId()function to add the ability to update userID attribute multiple times in a short period without losing the history of different end users. You can read our docs to learn about this fix. - Enhance the accuracy of device time calculation when it is changed by the mobile network.
- Resolve an ANR issue when the application reports events.
- Resolve an issue when exceptionMessage of a MobileHandledException doesn't display in query results.
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.