Gesture tracking not tracked on iOS (SwiftUI)?

[russellpeiris]

Question

Hello team,
I'm part of a team where they have a Swift iOS application, and an Android Kotlin Application. Both are instrumented with RUM. When I group by Action Type, I see that iOS has application_start and tap action types
But in Android, I see, scroll swipe back application_start and tap. Is this difference due to a limitation on RUM SDK for Swift?

[mariedm]

Hi @russellpeiris 👋

Both our UIKit and SwiftUI automatic instrumentations only report tap actions. Android indeed supports more gesture types out of the box. If you wish to track scroll or swipe, you can manually report them using the following APIs:

• RUMMonitor.shared().addAction(type: .swipe, name: actionName)
• RUMMonitor.shared().startAction(type: .scroll, name: actionName) / stopAction(type: .scroll, name: actionName)

Hope this helps clarify things!

[russellpeiris]

Thank you @mariedm ,

A follow up question. Usually, if an action results in an error we can see it through the Errors tab inside the Action event, or the action frustration type if any, (Example, error tap, error click). Will RUMMonitor.shared().addAction(type: .swipe, name: actionName)automatically record any scroll errors as Error scroll?

[mariedm]

• Error linking: errors occurring during an action's lifespan are automatically linked to the action and reported under the Errors tab indeed, and this works for all action types (tap, scroll, swipe, etc.).

• Frustration type: we don't have an errorScroll frustration type (see the supported options here. On iOS, only errorTap is supported and it only applies to tap actions.

• Manual API : using RUMMonitor.shared().addAction(type:name:) will automatically link errors and report frustration signals. However, as stated above, frustration signals (errorTap) are only added for .tap actions.

I hope this clarify things.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity and has the awaiting-response label.

It will be closed if no further activity occurs within 3 days.