javiersantos / javiersantos/BottomDialogs

Firebase Crashlytics detected an abnormal shutdown

Open
#48 0 comments 0 reactions 0 assignees View on GitHub
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!

![Cap 2021-05-10 19-05-02-982](https://user-images.githubusercontent.com/75154039/117642751-a1b99d00-b1c2-11eb-8306-e3509fec62b7.png)

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.