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.
Fixes
- Changed the default interval for sending event data from 10 minutes to 1 minute.
- Fixed an issue where mapping files aren't sent in DexGuard 9 with different flavor configurations.
- Fixed multiple crashes related to mobile session replay.
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
- Fix an issue that artifacts are missing for monoEnabled build
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
- Fix ANR cased by setUserId
- Fix ANR caused by blocking SecureRandom initialization during agent configuration
- Improve content length detection and limit reponsebody capture in okhttp3
- Fix few bugs in webview instrumentation
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
- Added session replay functionality for Jetpack Compose.
- Official session replay public preview version.
Fixes
- Fixed multiple session replay bugs.
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
- Fixed a
NullPointerExceptionissue in memory sampling process. - Added safe casting during the initialization of app launch times to prevent
ClassCastExceptioncompatibility in Microsoft Intune MAM SDK. - Improved okhttp callback protection to prevent agent crashes from user code exceptions.
- Fixed duplicated crashes from native crash reports.
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
- Added Gradle 9 Support
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.