Skip to content

v1.4.7

v1.4.7: Auto-track tap labels now resolve on SwiftUI buttons — closes the
@VistaApps-za VistaApps-za tagged this 27 May 05:50 
"Clicked an element" gap that buried real CTAs on the dashboard.

**Fixed:**

- The `UIWindow.sendEvent` tap-capture walked up only 4 ancestors
  looking for an `accessibilityLabel`. SwiftUI's button hosting tree
  is much deeper — `Button("Create Image") { … }` puts the merged
  accessibility label on a view 8–12 hops above the touched
  `Text` / `Image`. Bumped the walk-up to 16 ancestors so the label
  is reachable.
- New descendant-search fallback. SwiftUI's accessibility-merge
  model commonly puts the human-readable label on a SIBLING or a
  descendant of the hit-test target rather than an ancestor. When
  the ancestor walk-up returns nothing, the SDK now descends up to
  6 levels into the touched view's subtree looking for a `UILabel`
  with text or a view carrying an `accessibilityLabel`. First match
  wins — closest, shallowest descendant.
- New `textIndicatesPII` helper applies the same `password` /
  `card number` / `ssn` substring filter to descendant-found text
  as to ancestor accessibilityLabel — so a password field's visible
  text never lands on the wire.

Result: a SwiftUI `Button("Create Image") { … }` tap now ships
`element.clicked` with `accessibilityLabel = "Create Image"`, and
the Pages dashboard / live feed / per-person journey all render
**"Clicked 'Create Image'"** instead of "Clicked an element."
Assets 2
Loading