On this page:
On this page:
If an artifact has been updated, the version number of the updated artifact and its availability date are listed below. The version number corresponds to that shown on the download portal (http://download.appdynamics.com).
The most recent releases appear at the top of the page.
Mobile Agent Updates - March 21, 2019
The Mobile Agents listed in the table below now enable you to create session frames to name user screens more accurately. The session frames appear in the activity list of the Sessions Details dialog.
You can use the Mobile Agent/Plugin SDKs to name session frames based on the business context for a user flow. For example, you can name several session frames "Login", "Product Section", and "Purchase" to better represent the user activity.
Although you can now use the given Mobile Agents to create session frames, the session frames will not appear in the Session Details dialog until the upcoming Controller 4.5.8 release.
50.0 iOS Agent Update
Version 50.0.1512 – February 26, 2019
|MRUM-4480||iOS Agent crashes during AVAssetDownloadTask|
4.5.7 (Mobile Agent) Updates
The iOS Agent, Android Agent, and the Xamarin Agent now use version numbers different from that of the AppDynamics Controller and platform components. This change enables the Mobile Agents to be developed and released more quickly and with greater flexibility.
See Mobile Agent Version and Deployment Support Matrix to determine the minimum versions of the Controller and EUM Server required for supporting the latest features of the Mobile Agents.
4.5.6 HF1 (iOS Agent) Updates
Version 188.8.131.524 – February 4, 2019
|MRUM-4363||ANR stacktrace generation might cause host to crash|
4.5.6 (Mobile Agent) Updates
The hybrid application monitoring support for the Fetch API calls is disabled to avoid conflicts and errors.
4.5.6 (iOS Agent) Updates
Version 184.108.40.2067 – January 16, 2018
- The iOS Agent will display a warning message if another crash reporting tool is detected. You are recommended to use only one crash reporting tool to optimize the results and avoid conflicts.
- The iOS Agent enables you to configure whether to include stack traces when reporting errors.
4.5.6 (Xamarin Agent) Updates
Version 220.127.116.114 – January 16, 2018
You can now add error reporting for Xamarin applications. This enables you to report errors and exceptions and set severity levels using the Xamarin SDK.
4.5.5 (Android Agent) Updates
Version 18.104.22.1680 – December 11, 2018
|MRUM-4072||Infinite recursion bug on event listener instrumentation|
4.5.5 (iOS Agent) Updates
Version 22.214.171.1240 – December 11, 2018
- You can now manually disable crash reporting for the iOS Agent. This enables you to avoid conflicts and optimize crash report results when using other crash reporting tools.
4.5.2 (Android Agent) Updates
Version 126.96.36.1999 – October 9, 2018
- You can now manually and automatically upload DexGuard mapping files for Android. See Manually Upload Mapping Files and Automatic Upload Mapping Files.
carrierproperty attached to network requests and other events will now correctly be the SIM card operator name. This will reduce the number of unique carrier names and work even when the Android device is on Wi-Fi.
- The Android Agent, when configured to provide hybrid support, can monitor single-page monitoring.
|MRUM-3678||Filter out duplicate crash reports|
4.5.2 (iOS Agent) Updates
Version 188.8.131.524 – October 9, 2018
- The iOS Agent, when configured to provide hybrid support, can monitor single-page monitoring.
AppDynamics is ending official support and testing for iOS 6. To ensure that the iOS Agent monitors and reports correctly, you are highly recommended to use iOS 7+.
4.5.1 HF1 Updates
Version 184.108.40.20679 – September 12, 2018
|MRUM-3846||Allow users to manually toggle Sessions Enabled property for Mobile v/s Browser RUM|
Version 220.127.116.1147 – September 5, 2018
|MRUM‑3380||iOS ANR triggered with less than 2 seconds inactivity|
Upload doesn't work when using multidex
|MRUM-3725||Xamarin iOS: The beacons for app starts and for crashes are not sent when the application starts|
July 11, 2018
The new Code Issues Dashboard enables you to get trend and detailed information about caught non-fatal exceptions and instances of applications not responding (ANRs). The Android/iOS SDKs enable you to set the severity of caught non-fatal exceptions so that you can filter code issues by severity in Code Issues Analyze. See Code Issues for more information.
For some iOS ANRs, the wrong thread is marked as not responding