Android agent release notesRSS

Fixes

• Ensure interactions complete when an app leaves the foreground.

  Previously, it was possible for an interaction to persist across application foreground/background lifecycles if a trace segment was still in flight. This resulted in interaction traces extending past the default 60-second limit. Now, interactions are stopped when the app leaves the foreground regardless of segment states.

• Machine metrics continue generation upon app restore.

  Machine metrics now continue to generate after an app has been in the background and enters the foreground. Previously, they were only generated from launch until the app entered the background.

• Improve BitmapFactory instrumentation scoping.

  BitmapFactory’s static method instrumentation is now scoped to more tightly to its package and class to prevent instrumentation of similar but unrelated method signatures.

• Added more instrumentation to summary metrics.

  Now all instrumented methods are included in summarized category metrics including those only present in background threads.

• Added missing methods to HttpsUrlConnection instrumentation.

  Several missing proxy methods have been added to our HttpsUrlConnection shim. This restores the ability to override default HTTPS behavior.

Improvements

• New API methods for adding cross application tracing headers to noticeHttpTransaction().

  In case the New Relic agent doesn't support the HTTP API you're using, you can manually submit a transaction via the noticeHttpTransaction() method. With this release, this method now allows you to set the NR cross application tracing header for tracking purposes.

Fixes

• Fixed a rare build crash where newly constructed objects go unused and are later optimized down by ProGuard.

Improvements

• New API method for configuring logging verbosity.

  You can now choose how verbose the agent will be at boot by chaining withLogLevel() before your NewRelic start() call. The default level is INFO.

• New API method for renaming inflight interactions.

  Call NewRelic.setInteractionName() at the beginning of your onCreate() method to set a custom name for your interaction. This usually defaults to the name of the Activity subclass.

• Method tracing optimizations.

  We’ve carefully reviewed the code involved in tracing instrumented methods and reduced its CPU and memory overhead substantially.

Fixes

• Call checkcast before invoking NR instrumentation.

  This fixes an issue where the Dalvik VM refuses to load a class with our instrumentation in cases where the inbound object is not the expected type as determined by static code analysis.

• Don't attempt to instrument constructors in subclasses of classes we normally instrument.

  While we support instrumenting constructors by replacing the call to , we don't support doing this in subclasses. For now, we ignore these cases but may return to adding inline instrumentation to constructors in the future.

• Java 7u60 (pre-release) refactored the class in which we were storing our invocation dispatcher.

  We've future proofed the agent by storing the dispatcher in another core class.

Improvements

• End to end instrumentation for your mobile applications.
• Automatic instrumentation of important system objects and methods.
• Customizability to allow for instrumentation of your most important objects and methods.

Fixes

• Fixed rare bug in Eclipse where all projects are built with New Relic regardless of agent jar presence.

Improvements

• Added support for ProGuard with Ant builds.
• Clarified naming of unknown carriers on Android

Improvements

• Added support for ProGuard with Ant builds. *Note: Version 2.426.0 of the Android agent already works with ProGuard and other build systems (Gradle, Maven, and Eclipse).

Improvements

• The agent now detects if the app was instrumented properly and displays an error message if otherwise.
• The Eclipse plugin now refreshes your project after installing/updating New Relic.
• Improved post installation messaging in Eclipse.

Fixes

• Fixes an issue in Eclipse on Windows where Eclipse is installed in a location with a space in the path.
• Repackaged the agent with JarJar to prevent class space collisions.
• Fixes an issue where a re-used HttpRequest object would have multiple X-NewRelic-ID headers added.