New Relic Mobile for iOS is compliant with standard application stores, including Apple App Store, Google Play Store, Amazon Appstore, and others.
New Relic Mobile for iOS only monitors your app while it is in the foreground. The agent does not monitor background services while the app is closed.
Before you install and configure New Relic Mobile functionality with your mobile applications, make sure your iOS app meets these requirements for New Relic Mobile.
|New Relic Mobile||iOS requirements|
iOS 8 or higher
For Bitcode support, use SDK version 5.3.0 or higher.
NSURLConnection and AFNetworking are supported.
ASIHttpRequest networking APIs are deprecated as of iOS agent version 5.8.2.
Network traffic for UIWebView and WKWebView is supported. However, WKWebView Transfer size and Http errors are not supported.
Swift: Works with both network traces and crash reporting, but no interaction traces by default. Interaction traces must be enabled for Swift.
|Devices||Any iOS compatible device: iPhones, iPads, etc.|
|File sizes||New Relic Mobile adds about 2 to 12 megabytes to your iOS release app, depending on platform build.|
ARM 32-bit or 64-bit.
|SHA-2||As a standard security measure for data collection, New Relic requires that your application server supports SHA-2 (256-bit). SHA-1 is not supported.|
|Xcode||To take advantage of New Relic's iOS features, make sure you have the latest version of Xcode.|
Testing is not supported
New Relic Mobile agents are designed and tested to work in a normal app lifecycle. New Relic does not support running any testing environment on applications with the agent. Testing can cause conflicts and unpredictable behavior.
Potential method replacement conflicts
The iOS agent utilizes method replacement during run time. This may result in a conflict with other libraries that also implement method replacement, such as ReactiveCocoa, Aspects, and AppleGuice.