topic Re: Mobile app support for swiftui? in Open Q&A

Mobile app support for swiftui?

anders_lundin3 — Fri, 15 May 2020 14:41:50 GMT

We want to instrument a iOS mobile application buil on SwiftUI. Will this work nicely with Dynatrace mobile app SDK?

Re: Mobile app support for swiftui?

JamesKitson — Fri, 15 May 2020 15:17:27 GMT

Can find only a bit on this internally but it looks like it's not something that we will auto-instrument at least not at this time. But since it's just Swift I see no reason you couldn't manually instrument it using the iOS OneAgent SDK.

https://www.dynatrace.com/support/help/technology-support/operating-systems/ios/customization/oneagent-sdk-for-ios/

Re: Mobile app support for swiftui?

Patrick_H — Mon, 18 May 2020 05:59:58 GMT

I can confirm that pure SwiftUI is not yet supported, auto-instrumentation will not work for most UI elements and needs to be performed manually. Webrequest instrumentation will still work, but automatic linking to lifecycle action will not work for pure SwiftUI apps. In some scenarios automatic linking to manual actions might work. The SDK for manual instrumentation will work.

Re: Mobile app support for swiftui?

anders_lundin3 — Tue, 19 May 2020 06:24:36 GMT

Thanks for your input!

Re: Mobile app support for swiftui?

paul_kapeller — Mon, 26 Sep 2022 11:00:46 GMT

With the latest release of the iOS agent (8.249) we have implemented auto-instrumentation of SwiftUI. Further improvements are on the way.
For more info please visit the documentation.

Re: Mobile app support for swiftui?

marcelodesouza — Mon, 14 Jul 2025 14:21:02 GMT

Hi,

I am trying to override the captured control titles. I saw on the documentation the properties dtxCustomControlName, dtxCustomCellName and dtxCustomCellName.

Is there anything for SwiftUI?

I want to display something better than "Touch on CollectionViewCell @0:1" for example.
Thanks

Re: Mobile app support for swiftui?

paul_kapeller — Mon, 14 Jul 2025 14:51:01 GMT

Did you check our documentation in that regard? Is there any specific feature missing that you're looking after? https://docs.dynatrace.com/docs/observe/digital-experience/mobile-applications/instrument-ios-app/instrumentation/instrument-swiftui-controls#swiftui-control-labels

Re: Mobile app support for swiftui?

marcelodesouza — Mon, 14 Jul 2025 15:04:40 GMT

I did check this documentation before. I saw the option:

Button("Login", action: { /* perform login */ }).withCustomInstrumentationConfig(.useControlName("Login Button"))

But when I try to use useControlName, it says that is has not member with this name.

I checked the SwiftUIInstrumentationConfigParam and I only found those three options: skipInstrumentation, useDefaultControlName, doNotReportStateVariable

How do I set my own control name?

Thanks

Re: Mobile app support for swiftui?

irina_galata — Mon, 14 Jul 2025 15:59:27 GMT

The useControlName property was introduced in the 8.317 release of the iOS agent. This will work for most of the instrumented controls, such as buttons, toggles, pickers, sliders, etc.

However, in your case, "Touch on CollectionViewCell @0:1" is an action that is generated by the UIKit instrumentation of UICollectionView, which exists under the hood when you create a SwiftUI List. Currently, this naming can't be modified.

Re: Mobile app support for swiftui?

marcelodesouza — Mon, 14 Jul 2025 17:40:04 GMT

Is it a limitation from SwiftUI? Or is something that I can expect support from Dynatrace in the future? Thanks

Re: Mobile app support for swiftui?

irina_galata — Tue, 15 Jul 2025 05:51:46 GMT

Generally, we're much more limited in terms of instrumentation when it comes to SwiftUI due to its declarative nature. Currently, we can detect a SwiftUI list interaction when either its selection property changes or it contains navigation links (declared as NavigationLink or navigationDestination view modifier).
In all other cases, the instrumentation is handled by the iOS agent and not the SwiftUI instrumentor via the UICollectionView, and customising UIKit behavior from SwiftUI code is more complex.
We do, however, regularly reevaluate different approaches, and we may improve support in the future.