Android agent release notesRSS

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

Improvements

• Improved setup and configuration support, especially on Windows

Fixes

• Fixes an issue where HttpURLConnection responses could raise an unhandled exception
• Fixes an issue where reported response time is much shorter than actual response time under certain conditions
• Fixes an issue where certain HTTP requests could raise an unhandled exception