• /
  • EnglishEspañolFrançais日本語한국어Português
  • Se connecterDémarrer

iOS agent release notesRSS

October 19
iOS agent v7.7.9

Bug fixes

  • Fixed a crash (SIGSEGV or SIGBUS in SessionAttributeManager::generateJSONObject) on the harvest thread, which could also corrupt the heap and cause crashes elsewhere. The agent copied its internal session attributes, such as memUsageMb and lastInteraction, during a harvest without holding the lock that guards them, so it could read them while another thread was updating them. This issue was present in 7.7.8 and earlier.
  • Fixed the main thread blocking, and apps being terminated by the iOS watchdog (0x8BADF00D), once the event buffer was full and the app kept making network requests. The agent held a lock while it rewrote its on-disk copy of buffered events, and threads recording events, including the main thread, waited on that lock. Events dropped from a full buffer were also never removed from that copy, so it grew and was rewritten in full for every new event. Writes now happen without holding the lock, are batched, and dropped events are removed. This issue was present in 7.7.8 and earlier.
  • Fixed events occasionally going unreported when they were recorded, for example by a network request finishing, at the same moment the agent collected buffered events for a harvest. The agent cleared the buffer a second time after releasing its lock, which discarded any event added in between before it was sent. This issue was present in 7.7.8 and earlier.
  • Fixed the agent's own JSON work being recorded as app activity. NSJSONSerialization is instrumented for interaction traces, and the agent called it directly for every log message as well as for session attributes and handled exceptions. That added the agent's internal work to interaction traces and, when the app logged heavily, could overwhelm tracing. The agent now calls the original, uninstrumented implementation. This issue was present in 7.7.8 and earlier.
  • Fixed Session Replay accessibility identifier masking rules set in Application Settings being ignored on iOS. New Relic sends these rules to iOS apps with the identifier accessibilityIdentifier, but the agent only recognized tag, so every such rule was dropped. Both values are now accepted. A malformed rule is now skipped with a warning instead of discarding every rule or crashing the agent.
  • Fixed possible crashes in Session Replay masking. Masking lists could be updated by a reconnect, or by addSessionReplayMaskedAccessibilityIdentifier: and related APIs, while a frame was being captured, without holding the lock that capture uses. Custom masking rules containing values that can't be saved to NSUserDefaults, such as null, could also stop the app when the agent saved its configuration. Rules are now cleaned before they are stored, and every update to the masking lists is locked.
  • Fixed WKWebView navigations being reported without a URL in apps built with the iOS 27 SDK. With that SDK, WKWebView.URL can still be nil when a navigation starts. The agent now falls back to the main-frame request URL from decidePolicyForNavigationAction.
  • Fixed possible EXC_BAD_ACCESS crash when using addHTTPHeaderTrackingFor.

October 6
iOS agent v7.7.8

Bug fixes

  • Fixed an issue where calling recordError under low-memory conditions could terminate the host application. Error reports are now dropped and logged, and New Relic agent frames are trimmed from the top of the recorded stack.
  • Fixed a crash in NRMALoggerBridge::log caused by a missing argument in a log format string when removing session attributes. Corrected two additional invalid format strings in the same component.
  • Fixed an issue where distributed tracing timestamps (tracestate and payload ti) were sent in seconds instead of milliseconds when using the new event system.
  • Fixed an issue where successful MobileRequest events lost all distributed tracing attributes when a cross-platform SDK passed traceHeaders.
  • Updated the native agent to prevent adding duplicate distributed traces to requests reported with traceHeaders by Flutter, React Native, or other hybrid agents. This applies to both MobileRequest and MobileRequestError in both event systems.
  • Enforced minimum and maximum boundary limits for MaxEventPoolSize and MaxEventBufferTime configuration settings (maximum buffer time capped at 600 seconds).
  • Updated recordCustomEvent to return a boolean indicating whether the event was successfully added when using the new event system, rather than always returning YES.
  • Updated React Native JavaScript error uploads to pass the correctly cased ReactNative platform value, matching the Android agent behavior.

September 8
iOS agent v7.7.7

Nouvelle fonctionnalité

  • Mise à jour de la configuration de build XCFramework pour cibler une version de déploiement minimale d’iOS 15.0 et de tvOS 15.0, en s’alignant sur les exigences minimales documentées de la plateforme.

Débogage

  • Résolution d'un plantage (SIGSEGV dans objc_msgSend) survenant lors des lectures de configuration de la collecte. Huit propriétés d'objet sur NRMAHarvesterConfiguration déclarées comme assign conservaient des pointeurs pendants après le vidage du pool d'autorelease de la réponse /connect ou du dictionnaire NSUserDefaults.

  • Résolution d’un problème où toutes les traces d’activité étaient abandonnées pour une session lorsque la réponse /connect omettait l’attribut at_capture.

  • Correction de la valeur platform signalée avec les erreurs React Native pour qu’elle soit signalée comme ReactNative.

  • Correction du champ agentVersion dans la charge d’erreur JavaScript pour signaler avec précision la version de l’agent iOS plutôt que la version de la plateforme hôte.

  • Mise à jour de la validation de l’attribut personnalisé : le passage d’un objet NSArray ou NSDictionary en tant qu’attribut d’événement enregistre désormais un log d’erreur explicite identifiant le type non pris en charge, remplaçant le message d’avertissement générique "value must be an NSString, NSNumber, or BOOL".

August 13
iOS agent v7.7.6

Corrigé dans cette sortie

  • Correction du tri des événements Session Replay avant Meta/FullSnapshot.

  • Correction de données manquantes potentielles en réécrivant NRMAExceptionMetaDataStore.

  • Correction du script de téléversement de sourcemap RN.

  • Correction d'un problème potentiel de redémarrage de session dans checkAndHandleSessionTimeout.

August 7
iOS agent v7.7.5

Corrigé dans cette sortie

  • Correction d’un bug où l’appel de setUserId avec nil démarrait toujours une nouvelle session.

  • A empêché le téléchargement d’anciennes frames de Session Replay avec une nouvelle session.

  • A modifié reachability pour mettre à jour un rappel lors d’un changement au lieu de l’appeler à chaque fois.

  • Correction d'un plantage lié à l'invalidation hexadécimale.

  • A corrigé le plantage de setUserId vendorId.

  • Correction de l’atomicité dans les collections de traces NRMA.

  • Correction de setUserId pour qu’il reste synchrone.

  • Correction d'un plantage en faisant passer Session Replay d'un Timer à un DispatchSourceTimer.

  • Correction d’un plantage de CoreData NRMAMethodProfiler.

  • Correction d’un plantage en faisant en sorte que sessionAttributeJSONString prenne un instantané des dictionnaires.

  • Correction du texte MSR en limitant le décalage de compensation de largeur du texte SwiftUI à son contenu.

  • Correction d’une fuite de mémoire de JSErrorController.

  • Correction du texte MSR en faisant référence à la graisse de police numérique précise au lieu du trait de gras binaire.

  • A mis à jour les outils de téléchargement dSYM pour ajouter le paramètre appVersion à dsym-upload-tools run-symbol-tool.

  • A corrigé les modales SwiftUI manquantes dans MSR.

July 9
iOS agent v7.7.4

Nouvelles fonctionnalités

Les appareils simulateurs sont désormais signalés comme simulator-(deviceType).

Corrigé dans cette sortie

  • Suppression de la détection KMP qui causait une instabilité dans la version 7.7.3.
  • Correction d'un plantage qui pouvait survenir lors de l'enregistrement de requests web asynchrones.
  • Correction d'un plantage causé par une condition de concurrence de la configuration de harvest.

Droits d'auteur © 2026 New Relic Inc.

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