Also, it seems like deep links aren't going to the...

# compose-destinations

[dave08]

Also, it seems like deep links aren't going to their destination when the app is working in the background (only when closed completely, it works) and when coming from a link from Whatsapp... I don't know if it really concerns compose destinations -- but maybe I'm not using it right?

[Rafael Costa]

In regards to deep links, all we do is take the info from the annotation directly into:

navDeepLink {
    uriPattern = ....
    ...
}

[Rafael Costa]

from the official compose navigation APIs

[dave08]

Sorry to bother you about this again... just wondering if you know if the navigation component handles onNewIntent that gets sent when a new deep link is requested and launchMode in the AndroidManifest on my MainActivity is set to singleInstance...? I'm just maybe not understanding the inner workings of the component.

[dave08]

And is there a way to bypass the home screen when navigating to a deep link deeper in the hierarchy?

[Rafael Costa]

I sure hope so, that’s exactly what deep links are for, right?

[Rafael Costa]

But other than that, I’m not the most knowledgeable about deep links tbh. I think you’ll get better luck asking on #navigation-architecture-component or #compose

[dave08]

Ok thanks, I'll try.

[dave08]

No answer there... but the studio bot (Gemini) seems to say I need the navDeepLink { } in the composable(deepLinks = ...) function AND NavDeepLink to actually handle them... does compose destinations generate both?

[dave08]

Or maybe Gemini is wrong?

[Rafael Costa]

Yes, that is what CD does.

[Rafael Costa]

you can check the corresponding genrated Destination object. There is a "deepLinks" field that returns the deep links in the way you would have written yourself.

[Rafael Costa]

That gets called when registering the destination, with the composable() call.

[dave08]

Yeah, I saw that, but what about NavDeepLink composable?

[Rafael Costa]

how is that used? any documentation?

[Rafael Costa]

From the top of my head, i don't remember it

[dave08]

This is what gemini gave me:

@OptIn(ExperimentalNavigationApi::class)
val navGraph = navGraph(
    startDestination = "main",
    route = "root"
) {
    composable(
        route = "main",
        deepLinks = listOf(navDeepLink { uriPattern = deepLinkMain })
    ) {
        // Main screen content
    }
    composable(
        route = "sub",
        deepLinks = listOf(navDeepLink { uriPattern = deepLinkSub })
    ) {
        // Sub screen content
    }
}

@OptIn(ExperimentalNavigationApi::class)
@Composable
fun DeepLinkHandler(navController: NavHostController) {
    NavDeepLink(
        uriPattern = deepLinkMain
    ) {
        navController.navigate("main")
    }
    NavDeepLink(
        uriPattern = deepLinkSub
    ) {
        navController.navigate("sub")
    }
}

@OptIn(ExperimentalNavigationApi::class)
@Composable
fun MyComposable(navController: NavHostController) {
    NavHost(
        navController = navController,
        startDestination = "main"
    ) {
        composable(
            route = "main",
            deepLinks = listOf(navDeepLink { uriPattern = deepLinkMain })
        ) {
            // Main screen content
        }
        composable(
            route = "sub",
            deepLinks = listOf(navDeepLink { uriPattern = deepLinkSub })
        ) {
            // Sub screen content
        }
    }

    DeepLinkHandler(navController)
}

[dave08]

Maybe it's wrong...?

[Rafael Costa]

I've never seen such thing 🤷

[Rafael Costa]

I based my implementation on these official docs

[Rafael Costa]

https://developer.android.com/develop/ui/compose/navigation#deeplinks

[dave08]

Yeah... that's AI for you... it's not even a composable: NavDeepLink

[dave08]

https://developer.android.com/reference/kotlin/androidx/navigation/NavDeepLink?hl=en

[dave08]

Well, I guess my problem is somewhere else...

[Rafael Costa]

that NavDeepLink probably is something that gets instantiated internally

[Rafael Costa]

when we use the APIs provided by compose nav