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.
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.
👍 We just encountered the same issue (and we are New Relic's enterprise client as well)
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.
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/
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.
It still is, haven't gotten around updating the code yet - but with the new things learned in the blog this should be fixable.