Closed StefMa closed 4 years ago
I see two paths where finish()
wont be called, but they are both exceptional paths. Either way we will fix but it might point to integration issue. How are you calling takeOff
? If using autopilot, are you overriding isReady
?
Thanks for the quick response 👍 .
We are calling takeOff
and wait until the OnReadyCallback
calls onAirshipReady
:
UAirship.takeOff(application, airshipConfigOptions) {
// Doing something with Airship
}
Fixed in 13.3.0
Preliminary Info
What Airship dependencies are you using?
com.urbanairship.android:urbanairship-fcm:13.2.0
What are the versions of any relevant development tools you are using?
Android Studio something.. I guess this is unrelated to the bug.
Report
What unexpected behavior are you seeing?
Our crash reporting tool received this crash:
Please note that this crash happen currently only once for one device. But Airship is also not implemented that long and not used that much. So it may get more important in the future. But for now I just wanted to report it 🙃
What is the expected behavior?
I guess no crashes 🙃
What are the steps to reproduce the unexpected behavior?
Because I got this via our crash reporting tool I don't know how to reproduce.
Do you have logging for the issue?
Android: 10 Device: SM-G973F