Bug fixes
Fixed a performance issue where Session Replay image compression ran on the main thread. It now runs asynchronously, reducing overhead during capture.
Addressed rendering accuracy issues in Session Replay by emitting incremental view additions in their natural view order.
Fixed an issue where stale offline payloads could be sent by enforcing a time-to-live (TTL) that discards data queued too long.
Resolved an issue where session attributes could be lost during the shutdown harvest.
Fixed an issue where buffered events were dropped during app shutdown, ensuring they are now sent in the final harvest to prevent data loss.
Fixed a timing issue during device rotation where session continuity could be lost during the transition.
Made HTTP header handling thread-safe, resolving errors that could occur under concurrent access.
Fixed an issue where app start-up metrics could be miscalculated when a start-up timestamp was not set.
Resolved an issue where the agent attempts to report crashes without an active network connection, causing unnecessary errors on offline devices.
Fixed a native (NDK) crash that could occur during shutdown due to an ABI mismatch in
stop().Fixed ProGuard map upload for builds that produce a DexGuard APK directly.
Improved Gradle configuration-cache compatibility during map upload.
Relocated the bundled
commons-iodependency in the Gradle plugin to prevent conflicts with host applications.
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
- Fix an issue to prevent ANRMonitor from blocking the main thread on its own lock
- Fix a crash that is happening in android ndk agent v1.1.4
Support statement
- The Android NDK agent version 1.1.5 and above requires Android agent 7.7.6 and higher.
- 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
- Fix a crash in
newrelicTransformClasseswith ajava.lang.IllegalAccessErrorafter upgrading to AGP 9.1.0 - Fix a NullPointerException thrown from session replay textview section
- Fix an issue with
onTrimMemory()call in hybrid application
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.
Important notice
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.
Bug fixes
Fix an issue when initializing userId on first launch
Fix an issue in mobile session replay to capture z-index for React Native views
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
Fixed an OutOfMemory issue caused by payload data accumulating in SharedPreferences. Cached payloads are now persisted to disk and capped to prevent unbounded growth on devices with poor connectivity.
Resolved an ANR caused by repeated Binder IPC calls to ConnectivityManager on every reachability check. Network state is now tracked asynchronously via a registered network callback.
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.
Announcements
Session Replay for Android has moved from preview to general availability. Gain full visibility into your users' mobile experience with faithful visual reproductions of their sessions. Learn more about Session Replay.
New features
Added the ability to programmatically block specific views from being captured during Session Replay, giving fine-grained control over what is recorded beyond the default masking rules.
The agent now automatically creates a new session after 4 hours of continuous use, improving long-running session tracking.
Log forwarding now coordinates its sampling decisions with Session Replay, ensuring logs are captured for sessions that are being replayed.
Bug fixes
Resolved an issue where the agent attempted to forward logs without an active network connection, causing unnecessary errors on offline devices.
Fixed a RuntimeException that could occur when reading or closing streams from HttpsURLConnection.
Addressed a null pointer exception that could occur during session handling.
Fixed a timing issue where session rotation could occur before the harvest cycle completed, potentially causing data loss during the transition.
Resolved an issue where the session ID could be null during session rotation, causing data to be attributed incorrectly.
Addressed several rendering accuracy issues in Session Replay captures.
Fixed an issue where local masking configuration was not correctly applied to text elements during Session Replay capture.
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.
Important
A bug in this release causes all Session Replay text to appear masked as asterisks, regardless of the masking settings configured in the New Relic dashboard. Upgrade to v7.7.3 to resolve this issue.
Announcements
Session Replay for Android has moved from preview to general availability. Gain full visibility into your users' mobile experience with faithful visual reproductions of their sessions. Learn more about Session Replay.
New features
- Added the ability to programmatically block specific views from being captured during Session Replay, giving fine-grained control over what is recorded beyond the default masking rules.
- The agent now automatically creates a new session after 4 hours of continuous use, improving long-running session tracking.
- Log forwarding now coordinates its sampling decisions with Session Replay, ensuring logs are captured for sessions that are being replayed.
Bug fixes
- Resolved an issue where the agent attempted to forward logs without an active network connection, causing unnecessary errors on offline devices.
- Fixed a RuntimeException that could occur when reading or closing streams from HttpsURLConnection.
- Addressed a null pointer exception that could occur during session handling.
- Fixed a timing issue where session rotation could occur before the harvest cycle completed, potentially causing data loss during the transition.
- Resolved an issue where the session ID could be null during session rotation, causing data to be attributed incorrectly.
- Addressed several rendering accuracy issues in Session Replay captures.
- Fixed an issue where local masking configuration was not correctly applied to text elements during Session Replay capture.
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.
Fixes
- Use SecureRandom() for generating unique identifies
- Fix potential ANR on the main thread when using heavy load sampling
- Add exception handling for lower SDK version
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
- Add support for AGP 9
- Add error sampling for mobile session replay
- Add pauseReplay and recordReplay APIs
Fixes
- Multiple mobile session replay fixes for better performance
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.