material-components / material-components/material-components-android
BottomNavigationView: First Fragment onStart() Not Called on Startup in Material 1.13.0
@imhappi is already working on this.
Since Sep 15, 2025.
- Dominant language
- Java
- Stars
- 17.4k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
### 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.