Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Facebook Access token is not generating after integrate latest New Relic

android

#1

After implementing the new relic code. Facebook working stops.
Here is the comiple line:
implementation “com.newrelic.agent.android:android-agent:5.+”

A Facebook token is not generated after implementing new relic.

when we remove the new relic compline line and code. Then facebook working fine.

Thanks


#2

Hello!

Thank you for reaching out to New Relic support on the community forum and I’ll be helping you with this issue!

It looks like another person from your organization also reached out to us on the forum with a similiar question. Are you two working on the same application?

If so, I have opened an internal ticket with your colleague. Would you like to be added to the ticket?


#3

Yes, it’s my colleague. I think he has also faced the same issue. Actually Yesterday he is doing some R&D on this. Its very important can you fix this ASAP?


#4

Can you help me regarding this issue. Because I am waiting for response from new relic support team .


#5

This is serious issue in my application. Can you guide me ?. How I can fix this issue.


#6

I already reply your email and send the response and gradle files


#7

Hi Nitish,

I have been looking at your provided files on the internal ticket and will be responding there on the ticket.

@amit15 Would you like to be cc’ed onto Nitish’s ticket as he is your colleague and it is the same issue?


#8

Sure

Like you can directly coordinate with Nitish email. Once Nitish will resolve the issue. Same thing I will implement in my project.


#9

Hi there!

It looks like Nitish has temporarily resolved the issue by using New Relic 5.19.1. Please try that in your project and let me know if it works for you. I look forward to your reply.


#10

Hi @nitish & @amit15 -

I wanted to reach out and let you know that this issue has been rectified in Android Release version 5.21.0. You can update your Agent at any time to take advantage of this fix. I hope this helps you out!