I don't see why it bring stronger verification here, as the compiler should already help here.
I believe more in a K 2.2 compat problem.

@arnaudgiuliani
Thanks! That makes sense.
However, I think this behavior comes from the fact that navGraphRoute is declared as Any?.
In that case, the compiler won’t treat it as a String, so the String function overload isn’t resolved without explicit handling.
To me, this looks like expected Kotlin behavior rather than a K2.2 compatibility issue.

Do you have a test case to reproduce, something we can add into examples project, the android compose app?

@arnaudgiuliani
I've added test cases tosample-android-compose demonstrating the fix.

Added:

• Type-Safe navigation routes (NavigationGraphRoute,FirstScreenRoute,SecondScreenRoute)
• Two navigation examples:
  • Type-Safe Navigation (navigationTypeSafeGraph) - Uses@Serializable route objects
  • String-based Navigation (navigationStringGraph) - Uses traditional string routes
• Two screens sharing aSharedViewModel viasharedKoinViewModel
• Simple ViewModel to verify the same instance is shared between screens

You can test it by running the app and tapping "(>)Type Safe Navigation Example" or "(>)String Navigation Example". Both examples demonstrate that screens share the same ViewModel
instance (shown by matching instance IDs and shared timestamp), confirming the fix works correctly with Type-Safe routes.