IssueTracker

Arguments on actions are only used for Safe Args currently so your example would work if you switch to using Safe Args and the Directions classes it generates:

        actionOneBtn.setOnClickListener {
            navController.navigate(ArgFragmentDirections.actionOne())
        }
        actionTwoBtn.setOnClickListener {
            navController.navigate(ArgFragmentDirections.actionTwo(2))
        }
        actionThreeBtn.setOnClickListener {
            navController.navigate(NavigationDirections.globalAction())
        }

(I needed to make two changes to your XML to get it working: adding <argument android:name="type" app:type="integer"/> to action_two and changing the android:id for your root navigation element to "@+id/navigation")

We should fix NavOptions to parse arguments and pass them through, even if you're not using Safe Args.

Filed https://issuetracker.google.com/issues/111602491 for tracking supporting "@+id/navigation.xml"

Yes thank you, working as intended! Is it possible, to bind a UI (like nav bar,menu) to an action instead of a destination? That was my initial problem, although I wasn't sure if that is intended use at all. So tying a bottomNav bar to navigation actions, so that each action would have a default argument, that is passed to the same fragment, so the fragment would display different data each navigation. The fragment gets called, just the bundle is null.
It's in the bottomNavigation branch: https://github.com/2ma/NavigationActionBug/tree/bottomNavigation

An additional sample project that experiences the same issue can be found at the duplicate issue https://issuetracker.google.com/issues/118518636#comment6 - https://gitlab.com/thomas_herbeth/navigation-controller-poc

This is fixed by https://android-review.googlesource.com/845615 and will be available in Navigation 1.0.0-alpha09