• EnglishEspañol日本語한국어Português
  • ログイン今すぐ開始

iOS agent release notesRSS

September 12, 2018
iOS agent v6.3.2

Fixes

  • Fixed race condition in handled exceptions component, which had the potential of crashing on background inside std::recursive_mutex::lock()

tvOS agent v6.3.2

Fixes

  • Fixed race condition in handled exceptions component, which had the potential of crashing on background inside std::recursive_mutex::lock()

June 14, 2018
tvOS agent v6.3.2

Fixes

  • Replaced missing llvm bitcode in framework.

June 1, 2018
iOS agent v6.3.0

Improvements

  • Agent can now handle region specific application tokens.
  • Moved New Relic specific files out of users' "Documents" directory.

Fixes

  • Fixed inconsistency in deviceManufacturer session attribute; it will always be set as "Apple, Inc".
  • memUsageMb session attribute will now be stored as a numeric value rather than a string value.
  • Fixed race-condition in gesture instrumentation that could cause a crash on app background.
  • RequestUrl and RequestPath attributes on MobileRequest and MobileRequestError events will consistently be not URL-encoded.
  • Crash reports will now be uploaded immediately after processing on subsequent launch.
  • Fixed potential race-condition in +[NewRelic stopCurrentInteraction:(NSString*)activityIdentifier]; that could result in dead-lock.

tvOS agent v6.3.0

Improvements

  • Agent can now handle region specific application tokens.

Fixes

  • Fixed inconsistency in deviceManufacturer session attribute; it will always be set as "Apple, Inc".
  • memUsageMb session attribute will now be stored as a numeric value rather than a string value.
  • Fixed race-condition in gesture instrumentation that could cause a crash on app background.
  • RequestUrl and RequestPath attributes on MobileRequest and MobileRequestError events will consistently be not URL-encoded.
  • Crash reports will now be uploaded immediately after processing on subsequent launch.
  • Fixed potential race-condition in +[NewRelic stopCurrentInteraction:(NSString*)activityIdentifier]; that could result in dead-lock.

Bugs

  • Missing llvm bitcode (fixed in 6.3.1)

March 6, 2018
iOS agent v6.2.0

Improvements

  • Improved performance of symbol map upload script.
  • Improved performance of recordHandledException API.
  • Removed deprecated APIs.

Fixes

  • Prevents possible corrupted event data.
  • Event/Attribute APIs now accept NSNumbers containing BOOL values
  • +[NewRelic setApplicationVersion:] and +[NewRelic setApplicationBuild:] will now throw an exception if called after the agent is started.

March 1, 2018
tvOS agent v6.2.0

Improvements

  • Improved performance of symbol map upload script.
  • Improved performance of recordHandledException API.
  • Removed deprecated APIs.

Fixes

  • Prevents possible corrupted event data.
  • Event/Attribute APIs now accept NSNumbers containing BOOL values
  • +[NewRelic setApplicationVersion:] and +[NewRelic setApplicationBuild:] will now throw an exception if called after the agent is started.

February 9, 2018
iOS agent v6.1.1

Fixed in this release

  • Fixed an agent hang when relaunching an app after a crash. In some cases, the agent would appear to deadlock in the agent's startWithApplicationToken:appToken method after relaunching, which has been addressed.

December 14, 2017
iOS agent v6.1.0

New in this release

  • MobileRequestError events now contain the response body returned in the network request response, if one exists. Response bodies will only be reported if the http response body header capture feature flag is enabled. HttpResponseBodyCapture is enabled by default. Response body data will be limited to the first 4096 bytes (the Insights attribute limit).
  • MobileRequestError events now also contain any cross-application tracing (CAT) data returned in the response headers. See Introduction to cross-application traces for more information.

Fixed in this release

  • Fixed a memory leak in NRMAReachability.

tvOS agent v6.1.0

New in this release

  • MobileRequestError events now contain the response body returned in the network request response, if one exists. Response bodies will only be reported if the http response body capture feature flag is enabled. HttpResponseBodyCapture is enabled by default. Response body data will be limited to the first 4096 bytes (the Insights attribute limit).
  • MobileRequestError events now also contain any cross-application tracing (CAT) data returned in the response headers. See Introduction to cross-application traces for more information.

Fixed in this release

  • Fixed a memory leak in NRMAReachability.

Copyright © 2024 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.