在Jetpack Compose中从Activity的onCreate跳转至深层嵌套页面

方案1：Navigation Compose 深层链接 + 鉴权拦截（官方推荐） #

利用Navigation组件的深层链接能力，结合SplashScreen的鉴权逻辑，既符合官方规范，又能优雅处理带参数的深层跳转。

实现步骤： #

1. 配置深层链接到MessagesScreen
   在NavGraph中为MessagesScreen添加深层链接，指定匹配Uri并接收参数：

@Composable
fun AppNavGraph(navController: NavHostController, onAuthSuccess: () -> Unit) {
    NavHost(navController = navController, startDestination = "splash") {
        composable("splash") {
            SplashScreen(
                onAuthSuccess = {
                    // 鉴权完成后处理深层链接，再跳转到Home
                    navController.handleDeepLink(navController.context.intent)
                    navController.navigate("home") {
                        popUpTo("splash") { inclusive = true }
                    }
                }
            )
        }
        composable("home") {
            HomeScreen(navController = navController)
        }
        composable("conversation") {
            ConversationScreen(navController = navController)
        }
        // 配置深层链接规则
        composable(
            route = "messages/{conversationId}",
            deepLinks = listOf(
                navDeepLink {
                    uriPattern = "app://your-app-domain/messages/{conversationId}"
                }
            )
        ) { backStackEntry ->
            val conversationId = backStackEntry.arguments?.getString("conversationId")
            MessagesScreen(conversationId = conversationId)
        }
    }
}

2. 构建通知时指定深层链接PendingIntent
   创建通知时，直接使用深层链接生成PendingIntent，无需手动携带参数：

val deepLinkUri = Uri.parse("app://your-app-domain/messages/$conversationId")
val pendingIntent = NavDeepLinkBuilder(context)
    .setGraph(R.navigation.nav_graph)
    .setDestination(R.id.messages)
    .setArguments(bundleOf("conversationId" to conversationId))
    .createPendingIntent()

// 绑定到通知
val notification = NotificationCompat.Builder(context, CHANNEL_ID)
    .setContentIntent(pendingIntent)
    // 其他通知配置
    .build()

3. Activity初始化NavController
   无需手动处理Intent参数，直接初始化导航图即可：

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            val navController = rememberNavController()
            AppNavGraph(navController = navController)
        }
    }
}

优势：完全遵循Navigation组件设计规范，自动处理参数传递和跳转逻辑，无需手动维护全局状态，避免重复触发问题。

方案2：SharedFlow 事件驱动导航（轻量替代） #

如果不想用深层链接，可将原方案的全局字段替换为一次性消费的SharedFlow，避免配置变化或重复进入HomeScreen时的重复跳转。

实现步骤： #

1. 全局ViewModel定义SharedFlow

class GlobalNavViewModel : ViewModel() {
    private val _navigationEvents = MutableSharedFlow<String>(replay = 0)
    val navigationEvents = _navigationEvents.asSharedFlow()

    fun postNavigateToMessages(conversationId: String) {
        viewModelScope.launch {
            _navigationEvents.emit(conversationId)
        }
    }
}

2. Activity获取参数并发送事件

class MainActivity : ComponentActivity() {
    private val globalNavViewModel by viewModels<GlobalNavViewModel>()

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        intent.getStringExtra("conversationId")?.let { conversationId ->
            globalNavViewModel.postNavigateToMessages(conversationId)
        }
        setContent {
            val navController = rememberNavController()
            AppNavGraph(navController = navController, globalNavViewModel = globalNavViewModel)
        }
    }
}

3. HomeScreen收集事件并跳转

@Composable
fun HomeScreen(navController: NavHostController, globalNavViewModel: GlobalNavViewModel) {
    LaunchedEffect(Unit) {
        globalNavViewModel.navigationEvents.collect { conversationId ->
            navController.navigate("messages/$conversationId") {
                popUpTo("home") { saveState = true }
            }
        }
    }
    // HomeScreen界面内容
}

优势：事件为一次性消费（replay=0），不会因屏幕旋转等配置变化重复触发跳转，比普通State更安全可靠。

方案3：暂存参数 + 鉴权后跳转（极简方案） #

如果项目规模较小，可直接在Activity中暂存参数，待鉴权完成后触发跳转：

class MainActivity : ComponentActivity() {
    private var pendingConversationId: String? = null
    private lateinit var navController: NavHostController

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        pendingConversationId = intent.getStringExtra("conversationId")
        setContent {
            navController = rememberNavController()
            AppNavGraph(
                navController = navController,
                onAuthSuccess = {
                    pendingConversationId?.let { id ->
                        navController.navigate("messages/$id")
                        pendingConversationId = null
                    }
                }
            )
        }
    }
}

在SplashScreen完成鉴权后，调用onAuthSuccess回调即可。

优势：逻辑简单直接，无需额外依赖，适合小型项目快速实现。

内容的提问来源于stack exchange，提问作者jpegoraro