Android agent release notesRSS

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.

Gradle and Android Studio support

• Now you can add New Relic to your Gradle builds
• Android Studio support via Gradle/Maven

New Install Process

• Eclipse plugin support
• Maven Sonatype repository
• Simplified Ant installation

Eclipse

• Install via Eclipse plugin or Eclipse Marketplace
• Debug in Eclipse with New Relic

Maven

• Reference New Relic in pom.xml

Updated Agent API

• Control when New Relic starts
• Be sure to read our upgrade notes

Notes

New Relic for Android is now compatible with Android 2.2 (API Level 8)

• Fixes a scenario where the New Relic SDK could cause Android apps to crash when running on Android 2.2
• Fully supports network activity instrumentation and reporting on Android 2.2