From f1e0bc89ea16a97d3ffba99cefecd92c2ba65730 Mon Sep 17 00:00:00 2001 From: Marie Denis <29802155+mariedm@users.noreply.github.com> Date: Tue, 22 Jul 2025 18:13:08 +0200 Subject: [PATCH 1/2] [RUM mobile] Add note to SwiftUI action auto-instrumentation --- .../mobile_and_tv_monitoring/ios/advanced_configuration.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/advanced_configuration.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/advanced_configuration.md index f3e83cc1931cc..843fca503d917 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/advanced_configuration.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/advanced_configuration.md @@ -558,6 +558,7 @@ To automatically track user tap actions in SwiftUI, enable the `swiftUIActionsPr - The implementation differs between iOS 18+ and iOS 17 and below: - **iOS 18 and above:** Most interactions are reliably tracked with correct component names (e.g., `SwiftUI_Button`, `SwiftUI_NavigationLink`). - **iOS 17 and below:** The SDK cannot distinguish between interactive and non-interactive components (for example, Button vs. Label). For that reason, actions are reported as `SwiftUI_Unidentified_Element`. +- If you use both automatic and manual tracking, you may see duplicate events. This is a known limitation, and the only way to avoid this is to rely on a single instrumentation type. - You can use the default predicate, `DefaultSwiftUIRUMActionsPredicate`, or provide your own to filter or rename actions. You can also disable legacy detection (iOS 17 and below) if you only want reliable iOS 18+ tracking: {{< tabs >}} From cd7c30e4c5e29a419f63c1ad3b5f32e85d3f1cb2 Mon Sep 17 00:00:00 2001 From: Marie Denis Date: Wed, 23 Jul 2025 09:56:33 +0200 Subject: [PATCH 2/2] Apply Rosa CR comment --- .../mobile_and_tv_monitoring/ios/advanced_configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/advanced_configuration.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/advanced_configuration.md index 843fca503d917..6f19475960a93 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/advanced_configuration.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/advanced_configuration.md @@ -558,7 +558,7 @@ To automatically track user tap actions in SwiftUI, enable the `swiftUIActionsPr - The implementation differs between iOS 18+ and iOS 17 and below: - **iOS 18 and above:** Most interactions are reliably tracked with correct component names (e.g., `SwiftUI_Button`, `SwiftUI_NavigationLink`). - **iOS 17 and below:** The SDK cannot distinguish between interactive and non-interactive components (for example, Button vs. Label). For that reason, actions are reported as `SwiftUI_Unidentified_Element`. -- If you use both automatic and manual tracking, you may see duplicate events. This is a known limitation, and the only way to avoid this is to rely on a single instrumentation type. +- If you use both automatic and manual tracking, you may see duplicate events. This is a known limitation. To avoid this, use only one instrumentation type - either automatic or manual. - You can use the default predicate, `DefaultSwiftUIRUMActionsPredicate`, or provide your own to filter or rename actions. You can also disable legacy detection (iOS 17 and below) if you only want reliable iOS 18+ tracking: {{< tabs >}}