2

I'm getting a lot of crashes on this in my production application. I have not been able to reproduce it myself, and the crash stack trace does not mention any of my own files. As you can see on the crash overview, I get the same crash many different places.

Is this a bug in the bottom navigation library? Has anyone else experienced this?

Stack trace Crash list

Otziii
  • 2,304
  • 1
  • 25
  • 34
  • You have to replicate this to debug, have you tried this on multiple devices/OS? – Vikas Aug 11 '21 at 12:13
  • Hello, I guess before initialize the UI, if we access that view it will show this exception. – Tippu Fisal Sheriff Aug 12 '21 at 18:43
  • Looks very weird. Would be great if you show how you initialize and setup your BottomNavigationBar. – Eugene Troyanskii Aug 14 '21 at 17:14
  • 1
    Are you calling `popBackStack()` in your app and not checking the return result [as the docs say you should](https://developer.android.com/guide/navigation/navigation-navigate#back-stack)? It sounds like you've popped every destination off the back stack – ianhanniballake Aug 14 '21 at 20:33
  • 1
    @ianhanniballake I have not checked the return result on popBackStack() - I will test this! Thanks :) – Otziii Aug 16 '21 at 07:53

0 Answers0