javiersantos / javiersantos/BottomDialogs
Firebase Crashlytics detected an abnormal shutdown
- Dominant language
- Java
- Stars
- 632
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Description
Hello. Thank you for providing this feature. I'm using it well. However, Firebase CrashLytics recently detected NPE in BottomDialogs related code. I don't know the details, so I'll upload the captured picture.
Thank you!

Contributor guide
No contributing guide indexed for this repository
Research direction
The report provides only a Firebase Crashlytics NPE and an uploaded screenshot, with no file, test, stack trace, or reproduction steps. Start by extracting the stack trace from the screenshot and locating the referenced BottomDialogs code, then establish the abnormal-shutdown path before defining a fix. Done requires a reproducible failure and verification that the shutdown no longer triggers the NPE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100