BottomNavigationView: First Fragment onStart() Not Called on Startup in Material 1.13.0

[GH860]

Description

After upgrading to com.google.android.material:material:1.13.0, the first fragment (start destination) in a BottomNavigationView setup with multiple navigation graphs does not trigger onStart() on app startup(just onCreate triggres). Switching to another tab and returning to the first fragment triggers onStart() correctly. Downgrading to 1.12.0 resolves the issue, indicating a regression in 1.13.0.

Expected Behavior

The start destination fragment’s onStart() should be called on app startup when the BottomNavigationView loads the first nav graph.