discuss.newrelic.com Open in urlscan Pro
162.247.242.36  Public Scan

URL: https://discuss.newrelic.com/t/android-failed-to-detect-new-relic-instrumentation-still/161519
Submission: On September 23 via api from US — Scanned from DE

Form analysis 1 forms found in the DOM

POST /login

<form id="hidden-login-form" method="post" action="/login" style="display: none;" __bizdiag="695534669" __biza="WJ__">
  <input name="username" type="text" id="signin_username">
  <input name="password" type="password" id="signin_password">
  <input name="redirect" type="hidden">
  <input type="submit" id="signin-button" value="Log In">
</form>

Text Content

Products
Pricing
Solutions
Help Center
About

Learn

 * Docs
 * Build on New Relic
 * Explore open source projects
 * Training

Get Help

 * Community forum
 * 
 * Global technical support
 * Expert services

New Relic One

 * Platform Overview
 * Telemetry Data Platform
 * Full Stack Observability
 * Applied Intelligence

By Topic

 * DevOps
 * Cloud Adoption
 * Native
 * Digital Customer Experience

By Industry

 * E-Commerce and Retail
 * Media
 * Public Sector

By Technology

 * Amazon Web Services
 * Pivotal Cloud Foundry
 * Microsoft Azure
 * Google Cloud Platform
 * Kubernetes
 * 

Our Customers

Over 17,000 customers love New Relic, from Fortune 500 enterprises to small
businesses around the globe.

Our Blog

The latest news, tips, and insights from the world of New Relic and digital
intelligence.

Our Company

 * About Us
 * Leadership
 * Meetups and Events
 * Resources
 * Social Impact

 * Investor Relations
 * Newsroom
 * Partner Program
 * Contact Us

Log InSign Up
 * 
 * 

We've updated this site, please refresh, or you may experience unexpected
behavior.



WELCOME TO THE NEW RELIC COMMUNITY FORUM!

This is a public forum for users to discuss questions around software analytics,
performance monitoring, and using New Relic products.

To participate, just Log In with your New Relic account. Make sure to also
review our Community Guidelines, Terms of Service, and Privacy Policy.

X





[ANDROID] FAILED TO DETECT NEW RELIC INSTRUMENTATION STILL

Support: Full-Stack Observability (FSO)Mobile
android new-moderation-topic

You have selected 0 posts.

select all

cancel selecting

Sep 16
1 / 7
Sep 16

23h ago

phillip6
1
7d


(I read some old topics first, but nothing helpful for my situation)

I am trying to use the Android agent along with a module builder from Titanium
to create a New Relic module to support us in Titanium 9+

I used these directions for how to use New Relic Android agent: Install Android
apps with Gradle and Android Studio | New Relic Documentation

And these directions for Titanium: Android Module Quick Start

For New Relic I used the newest 6.2.1 and everything seemed to compile okay.
After running it, I get this error from New Relic:

[ERROR] E/com.newrelic.android: Failed to detect New Relic instrumentation. The
current runtime variant may be excluded from instrumentation, or instrumentation
failed during your build process. Please visit http://support.newrelic.com.

Based on previous topics, it is not so clear where this could be - but I would
love some ideas of things to look at. This is a blocker for my application
upgrade to Titanium 9 and it would be great to get this piece up and going.





 * CREATED
   
   7d

 * LAST REPLY
   
   23h
 * 6
   
   REPLIES

 * 164
   
   VIEWS

 * 2
   
   USERS

 * 1
   
   LINK

 * 5
   

cmancusoNR Support
3d


Hi @phillip6 New Relic has deprecated Titanium support and is now considered an
open source project. If you haven’t already, I would suggest taking a look at
the GitHub repo to see if any of the information on there may be of use to you:
https://github.com/newrelic/titanium_mobile 1

1 Reply



phillip6
cmancuso
2d


Thanks for letting me know, yes, I have looked at that and in this case, I am
trying to build my own module and just use the Android New Relic Agent directly
- that is where the error is coming from.

So the question is about that error coming from the Android New Relic Agent,
since I am comfortable wrapping it up in a Titanium module myself.




phillip6
2d


also, unless I am really overlooking it, that titanium_mobile module does not
seem to have a lot of newrelic specific module code, it all looks really
Titanium related - but not much guidance about how to get newrelic agents
working in Titanium. Am I maybe overlooking something @cmancuso ?

1 Reply



cmancusoNR Support
phillip6
1d


Hi @philip6 that error usually points to a configuration error with the Android
agent. Could you confirm if you have followed the steps in this documentation:
Install Android apps with Gradle and Android Studio | New Relic Documentation

Some often overlooked steps are adding apply plugin: 'newrelic' in your app
level build.gradle file

To start New Relic’s mobile monitoring agent: In your Default Activity (as
defined in your Manifest), import the NewRelic class - import
com.newrelic.agent.android.NewRelic;




phillip6
23h


Yes, I did start with those steps and I will continue working on it. I am not
sure how that apply plugin command works in the build.gradle file - but when I
tried that it caused a failure in my build process, so it must somehow need
something else to bring it in.

What I wonder is if the message I am seeing is based on a FeatureFlag or based
on the agent version I am trying to use.

What is also odd is that in my module project where I am trying to include
agent-gradle-plugin - it does not compile properly, I have to include
android-agent to even get it to compile.

Not sure if that is based on how our project is set up or what, but I do get
compilation to happen…just still see that error message.




phillip6
23h


Another reason I ask about the agent version is because in 6.2.1 I see:

[INFO] I/com.newrelic.android: isInstrumented: checking for Mono instrumentation flag - NO
[ERROR] E/com.newrelic.android: Failed to detect New Relic instrumentation. The current runtime variant may be excluded from instrumentation, or instrumentation failed during your build process. Please visit [http://support.newrelic.com](http://support.newrelic.com/)


and then only changing the version back to 5.23.0 with no other code changes,
the error changes to:

[INFO]  I/com.newrelic.android: isInstrumented: checking for Mono instrumentation flag - NO
[ERROR] E/com.newrelic.android: Failed to detect New Relic instrumentation.  Something likely went wrong during your build process and you should visit http://support.newrelic.com.









THIS TOPIC WILL AUTOMATICALLY CLOSE IN A YEAR.


Reply


SUGGESTED TOPICS

Topic Replies Views Activity New Relic sends start application event for the
another application
Mobile
android bug
3 332 Jun 24

SwiftUI support for iOS Agent?
Mobile
ios ios-agent
3 367 Jul 5

NoSuchMethodError putIfAbsent Android Agent 6.1.0 in Android API Level 21
Mobile
mobile android
2 506 Jul 13 Is NR iOS agent track the user interaction events?
Mobile
mobileapm
3 323 21d Android Agent 6.1 not sending network request metrics
Mobile
android agent
1 263 Jul 22


WANT TO READ MORE? BROWSE OTHER TOPICS IN MOBILE OR VIEW LATEST TOPICS.


[EN.SHARE.TOPIC]



Share



COMPANY

 * Careers and Culture
 * Partner Program
 * Investor Relations
 * NewRelic.org
 * Suppliers Portal

CONNECT

 * Contact Us
 * Request Demo
 * Events

INTERNATIONAL

 * newrelic.jp (日本語)
 * newrelic.fr (Français)
 * newrelic.de (Deutsch)
 * newrelic.co.kr (한국어)

 * 
 * 
 * 
 * 
 * 

©2008-20 New Relic, Inc. All rights reserved
  Terms of Service   Community Terms of Service   DMCA Policy   Privacy Policy
  Cookie Policy   UK Slavery Act of 2015

Invalid date Invalid date