Android agent release notesRSS

Fixed in this release

• Fixed instrumentation failures introduced in the 5.17.0 release.
• Corrected a hang during instant app shutdown that could occur during a crash.

Fixed in this release

• Fixed trace instrumentation crash introduced in 5.17.0 release.

New in this release

• Added instrumentation support for Android Instant Apps The agent now detects and instruments all feature modules for an instant app. Because instant apps are typically side-loaded, users must add NewRelic.start() calls to each entry point activity in the module. We've also created a document to help integrate the agent into your Instant App. See Install the New Relic plugin for Android Instant Apps for more information.

Fixed in this release

• Correctly restore any pre-existing unhandled exception handler when the agent shuts downs. Maintain the state of existing unhandled exception handlers when the agent returns to foreground.
• Fixed instrumentation of abstract classes derived from Android SDK classes.
• Fixed instrumentation failure when using certain Java 8 features, such as lambdas.
• Updated instrumentation support for Dexguard 8 on Android Studio 3.0.
• Enforce @SkipTrace with Android SDK-derived classes. Previously, onCreate() and onCreateView() could not be skipped from Activity, Fragment and other SDK classes.

New in this release

• MobileRequestError events now contain the response body returned in the network request response, if one exists. Response bodies will only be reported if the withHttpResponseBodyCaptureEnabled feature flag is enabled. HttpResponseBodyCapture is enabled by default. Response body data will be limited to the first 4096 bytes (the Insights attribute limit). A content type attribute will also be added to the event if a "content_type" header is found in the response.
• MobileRequestError events now also contain any cross-application tracing (CAT) data returned in the response headers. See Introduction to cross-application traces for more information.

Fixed in this release

• Stream file handle usage during class instrumentation has been tightened up to prevent potential resource leaks.
• Proguard map detection of release variants when using AndroidStudio 3 has been restored.
• Add content type parameter missing from HTTP error traces when instrumenting OkHttp2, OkHttp3 and Retrofit requests.

New in this release

• The NetworkRequests feature flag is now enabled by default. The feature can still be disabled (and re-enabled) at any time if the additional MobileRequest events are not needed.
• Added a feature flag for MobileHandledException events (FeatureFlag.HandledExceptions). Handled exception reporting is enabled by default; use this flag to globally disable the feature.

Fixed in this release

• Crash reports are again uploaded immediately, rather than during the next scheduled harvest.
• Correctly detects Proguard/Dexguard-enabled apps, and uploads their mapping.txt files to the symbol upload collector.
• Restored missing instrumentation of Square Retrofit2 classes.
• Added missing response codes from HttpURLConnection POST requests.
• The MobileRequest event byteSent attribute has been renamed to bytesSent. Any Insights queries using byteSent must be updated to maintain accuracy.

New in this release

• The agent has added API methods to report handled exception events to Insights! Details and examples of how to use the new APIs can be found in the Android SDK API document recordHandledException. We've also updated the document that describes how to query handled exception events from Insights: Insights query examples for New Relic Mobile provides useful queries for examining handled exception event data. Apps that use Proguard or Dexguard may have to make adjustments to their Proguard configuration to preserve all exception information. Please review Configure ProGuard or DexGuard for Android Apps for more details.
• Added support for automatic instrumentation when using Android Gradle plugin version 3 (used by Android Studio 3).

Fixed in this release

• HttpURLConnection requests now return the correct status codes in MobileRequest events
• Report carrier type as 'Unknown' if a valid carrier type can not be determined
• Restore instrumentation of Android support classes (missing since version 5.13.0)

This release has been removed due to deployment issues with Jcenter. Please use release version 5.15.1 instead.

### New in this release

• The agent has added API methods to report handled exception events to Insights! Details and examples of how to use the new APIs can be found in the Android SDK API document recordHandledException. We've also updated the document that describes how to query handled exception events from Insights: Insights query examples for New Relic Mobile provides useful queries for examining handled exception event data. Apps that use Proguard or Dexguard may have to make adjustments to their Proguard configuration to preserve all exception information. Please review Configure ProGuard or DexGuard for Android Apps for more details.
• Added support for automatic instrumentation when using Android Gradle plugin version 3 (used by Android Studio 3).

### Fixed in this release

• HttpURLConnection requests now return the correct status codes in MobileRequest events
• Report carrier type as 'Unknown' if a valid carrier type can not be determined
• Restore instrumentation of Android support classes (missing since version 5.13.0)

New in this release

• The agent now reports network request events to Insights! This feature must be enabled when starting the agent using the NetworkRequests FeatureFlag. When enabled all network calls will be tracked, in addition to network errors.

  We've also added a new document that describes how to query network events from Insights. Mobile Request Query Examples provides useful queries for examining network request event data.

Fixed in this release

• Ensure there is no shared activity history state between launched sessions.

New in this release

• Added a new MobileBreadcrumb event type that allows you to annotate the execution of your app, to help troubleshoot crashes and provide greater detail in Insights. See the recordBreadcrumb() API docs for more information.
• Added an additional recordCustomEvent method that takes the event name as an optional parameter. This avoids the need to add a name attribute in the passed attribute set. See the recordCustomEvent() API docs for more information.