Android Troubleshooting Framework Install and Configuration

  1. Follow Android Agent Installation Guide: Install Android Apps with Gradle and Android Studio (Latest Agent version recommended: Android Agent Release Notes)

  2. Agent start call is in default activity (as defined in the manifest). Avoid the Application class as this can lead to incorrect data reporting, most commonly, inflated app launch count.

  3. Android dependencies are added to App and Project gradle files, and agent version numbers match between files

  4. Additional dependencies meet version requirements outlined in New Relic for Android Compatibility and Requirements to avoid conflicts.

  5. Configure ProGuard/DexGuard rules

  6. Enable/Disable agent feature flags as desired, and place them before agent start: Android Agent Configuration and Feature Flags

  7. Add Custom Data: Android Add Custom Data (Ensure any customized data is called after the agent’s start call)

  8. Check the agent’s messages in the console for more details if there are any data reporting issues: Android Agent Configuration and Feature Flags: Logging (AUDIT log level recommended)


NewRelic.withApplicationToken("YOUR_APP_TOKEN")

.withLogLevel(AgentLog.AUDIT)

.start(this.getApplication());

  1. Adjust the agent’s harvest cycle timer, or event pool to prevent data loss caused by harvest data limits:
  1. If the you are still experiencing issues after installing the Android agent in accordance to the Installation Documentation, please contact support and provide the following:
  • App and Project level gradle files

  • ProGuard/DexGuard rules

  • Logcat output demonstrating the issue with the agent’s logging enabled and set to AUDIT

  • Run ./gradlew clean bundle -d | grep \\[newrelic and send the resulting log

  • Link to the application in the New Relic portal that is experiencing issues