Closed ninovanhooff closed 2 years ago
@ninovanhooff Really sorry, I most of missed the github notification in my email. Are you still experiencing this crash?
I am not having any luck reproducing this, but it seems other have had issues with using a mismatched jdk to build, not sure how you would get into that state. Ill have @jyaganeh take a look as well
Hi @ninovanhooff, I haven't been able to reproduce this but it looks like it may be a proguard/minification issue? If you do have minification enabled, would you mind sharing the proguardFiles
line from your build.gradle
file and any custom rules you may have set up?
Also, has this continued to only impact Galaxy J5 devices on Android 9 or does Firebase now show additional reports? How many users/crashes are you seeing?
There was a spike for this issue on a single day for a single user. Haven't seen it since, so this issue can be closed AFAIC.
Thanks for your efforts :)
Thanks for the update!
Preliminary Info
What Airship dependencies are you using?
core, fcm, automation @ 15.1.0
What are the versions of any relevant development tools you are using?
Android Studio Arctic Fox | 2020.3.1 Patch 3 Build #AI-203.7717.56.2031.7784292, built on October 1, 2021 Runtime version: 11.0.10+0-b96-7281165 x86_64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 11.6 GC: G1 Young Generation, G1 Old Generation Memory: 4096M Cores: 16 Registry: external.system.auto.import.disabled=true, debugger.valueTooltipAutoShowOnSelection=true, ide.balloon.shadow.size=0 Non-Bundled Plugins: com.dubreuia, com.intellij.marketplace, com.jetbrains.ChooseRuntime, hunspell, mobi.hsz.idea.gitignore, Dart, org.jetbrains.kotlin, zielu.gittoolbox, io.flutter, com.developerphil.adbidea
Report
What unexpected behavior are you seeing?
On Galaxy J5 (Android 9), a crash occurs regarding a method that could not be found
What is the expected behavior?
No crash
What are the steps to reproduce the unexpected behavior?
Looking at the stack trace, this occurs when initializing Airship / at app startup. Not completely sure as I don't have this device myself. Found this issue in Crashlytics.
Do you have logging for the issue?