Deeplinking in iOS

[jmgoree]

Are there any examples of passing an iOS universal link to decompose. I have successfully implemented on the Android side, however need some assistance/ideas on how to accomplish it on the iOS side.

I am able to capture the url in the swift code here:
`@main
struct iOSApp: App {

let Logger: DatadogLogger
@StateObject private var deeplink = Deeplink()
@UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate

init() {
    self.Logger = DatadogLogger()
}

var body: some Scene {
	WindowGroup {
        ContentView()
            .environmentObject(deeplink)
            .onOpenURL(perform: { url in
                print ("before " + String(deeplink.publicUserId))
                deeplink.publicUserId = (!url.absoluteString.isEmpty ? Int(url.lastPathComponent) : -1) ?? -1
                print ("after " + String(deeplink.publicUserId))
        })
	}
}

}`

However the problem i have is passing that data to the compose code to recreate/update the mainviewcontroller. Is there an iOS equivalent of the android handleDeeplink?

[arkivanov]

Please take a look at Confetti, it has an example of deeplinking on iOS.

[jmgoree]

Thanks Again for the help! After debugging a bit more, if i dont use compose in the shared code to drive the UI. Deeplinking works. However once i use that path from iOS the changes/new instance doesnt update the compose code. I need to investigate possibly building a shared flow or similar that the compose side could listen to and change accordingly. But that seems like recreating what the @published and new instance creation already should do

[arkivanov]

I didn't try yet, but you may need to wrap the component with MutableState somehow. I could try later if that didn't work

[jmgoree]

Interesting, I'll play around with it but if you happen to come across any examples I'd greatly appreciate it. Again thanks for the help

[arkivanov]

After thinking more about it, since you are using Compose, I think you don't need @Published for the root component. You can try creating the following Kotlin class next to your root MainViewController. Then try using it in your Swift app delegate instead of @Published, and call set when a instance of the root component is created. Pass the holder to your MainViewController and use the component from there. This should make your composable recomposing on component change.

class RootComponentHolder(component: RootComponent) {
    internal val component = mutableStateOf(component)

    fun set(component: RootComponent) {
        this.component.value = component
    }
}

[jmgoree]

@arkivanov Thanks that worked. I ended up taking it a step further and letting that "holder" class notify the app as a whole via a shared flow to gracefully handle new info provided from the deeplinks/anything external to compose.