Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatibility with New Relic #21

Open
steipete opened this issue May 16, 2014 · 6 comments
Open

Incompatibility with New Relic #21

steipete opened this issue May 16, 2014 · 6 comments

Comments

@steipete
Copy link
Owner

steipete commented May 16, 2014

Currently this is incompatible with New Relic. We informed their support and I'd love to help, but since their framework is closed source and "protected" against disassembling, I don't see how I can help :/

We have to wait and hope that they are looking into it.

screen shot 2014-05-16 at 10 13 43

@steipete
Copy link
Owner Author

steipete commented May 20, 2014

This has been reported to New Relic a week ago, but sadly they don't see it as important enough to look into, even though it affects some of their enterprise customers.

@luca-bernardi
Copy link

luca-bernardi commented May 20, 2014

👍 We just encountered the same issue (and we are New Relic's enterprise client as well)

@steipete
Copy link
Owner Author

steipete commented May 20, 2014

Please write them so they assign this an engineer. I'm happy to help them but can't solve this on my own without understanding what they do.

@steipete
Copy link
Owner Author

steipete commented Jul 3, 2014

I'm finally making progress here. Looks like I have to change the way we do swizzling: http://blog.newrelic.com/2014/04/16/right-way-to-swizzle/

@esttorhe
Copy link

esttorhe commented Jul 18, 2014

Just out of curiosity; this is still an issue right?

Just wondering if I could use this to configure some tracking methods with Crashlytics although the application currently uses NewRelic and I'm assuming its not going to work.

@steipete
Copy link
Owner Author

steipete commented Jul 18, 2014

It still is, haven't gotten around updating the code yet - but with the new things learned in the blog this should be fixable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants