We're still working on improving the SwiftUI instrumentation process for mobile applications. If you face any issues while instrumenting SwiftUI controls, please contact a Dynatrace product expert via live chat within your Dynatrace environment and provide the log file of the affected build. You can find the log file of the most recent build at dynatrace_instrumented/current/instrumentation.log. Log files of previous builds are located in time-stamped archives under dynatrace_instrumented.
Instrumentation already running
If you've run into an issue with the Dynatrace SwiftUI instrumentor and it hasn't been restored automatically, perform the steps described below.
- Stop the
DTSwiftInstrumentor process if it still exists.
- If you see the changes made by the SwiftUI instrumentor in your project's source code, run the following command in the project root:
DTSwiftInstrumentor restore . if you installed the instrumentor via Homebrew.dynatrace/DTSwiftInstrumentor restore . if you installed the instrumentor manually
DTSwiftInstrumentor exited with an error while processing <filename>
Our SwiftUI instrumentor binary has crashed. Please contact a Dynatrace product expert via live chat within your Dynatrace environment and provide the log file of the affected build.
Unable to check if other instances of the instrumentor are running because user script sandboxing is enabled
When the SwiftUI instrumentor starts, it checks whether other instances of the instrumentor are already running. When user script sandboxing is enabled or when you use a project created in Xcode 15+ (where this feature is on by default), this check doesn't work out of the box, and the instrumentor can't initialize.
To solve this issue, disable user script sandboxing (ENABLE_USER_SCRIPT_SANDBOXING project flag).
