On this page
Check the screen sequence in your iOS recordings and give SwiftUI destinations stable names. Initialize the SDK and allow collection before testing navigation.
Version covered: 1.1.11. Requires iOS 15 or later.
Check UIKit navigation
The SDK observes native view-controller appearances. Run a journey through your existing controllers and compare the recorded sequence with the screens you visited, including presented controllers and Back navigation.
A container controller and the content it displays may be different parts of your app. Check the actual recording before relying on a controller name to describe a user-facing destination.
Name SwiftUI screens
For meaningful SwiftUI names, add the screen modifier to your actual screen:
import AnalyticsSDK
CheckoutView()
.trackScreen(name: "Checkout")
Use stable names without customer data or navigation arguments. Do not assume this modifier has the same semantics as native Android 1.2.0's screen label API.
Verify screen names
Start on the initial screen, open a nested destination, return and present a modal. Check the recorded names after collection starts and after it resumes. Test destinations whose content changes without navigation.
Use a screen name to describe a destination. Send completed outcomes through custom events. If the sequence or name is missing, follow iOS troubleshooting.