-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash: java.lang.AbstractMethodError in com.google.firebase.installations.remote.FirebaseInstallationServiceClient.readGenerateAuthTokenResponse #3507
Comments
I found a few problems with this issue:
|
Hi @omarkilani, thanks for reporting. Are you also using other Firebase products? Since In that case, could you try using BoM version instead of individual versions for each Firebase product, and see if that fixes the issue? Relevant code:
Thanks! |
Hi @argzdev, We don't use any other Firebase products. The only Firebase dep is:
The only other thing we do is disable analytics in the manifest:
We'll try the BOM way, but... is it weird that the exception isn't reproducible? I can't map the line number in the exception to the line number in the GitHub repo so it's hard to tell exactly where it's crashing. |
@argzdev I've pushed a new version of the app (com.rememberthemilk.MobileRTM / 40519) with the BOM change.
Since we can't repro it, we basically just have to deploy to users and see the crash data in Play Console. Will keep you updated. |
Thanks for the update, @omarkilani. That is an odd issue. For what it's worth, you could try cleaning or rebuilding your app before creating a new version of the app. I hope the changing the BoM version helps. For now, let's keep this ticket open until you have some update, and in case our engineers might have an idea what the issue is. Feel free to add any questions or extra information. Thanks! |
@argzdev thanks for the response. The app is always built from a clean checkout, and always with "clean" passed to Gradle on the command line. |
This makes the issue all the more odd. But anyhow, let's keep this open for now. Thanks for confirming! |
@argzdev still waiting on Play Store to approve the update, but... It seems like maybe... the crashing users are going down a different code path than us? Maybe their token request is failing in some way? Is there any way for you guys to check like... any changes to the FCM endpoints since Feb 22? And maybe aggregate crashes in the FCM code across apps? |
4.5.19 still crashes, so I'm not sure what to do next.
Etc. |
FWIW, this is what the Play Console looks like for this crash. We still can't repro. One of our users sent the unmapped crash, which looks like: I'm not really sure which method it's referencing here, because: None of these have an I thought maybe |
Just a random observation but... Bumps deps on play services ~Feb 14, and we rebuilt on Feb 22... probably a coincidence...? |
One thing I forgot to mention in the initial post is that we use/have used R8
|
We've made the following change to our proguard config:
And are now testing this change on the installed base of the app (version 4.5.20 / versionCode 40520). |
@argzdev the proguard rules in #3507 (comment) seem to have resolved these crashes. It's not really clear why they're needed now, but maybe this is useful information for... someone? Thanks! |
Hi @omarkilani, thanks for the updates! I'm sure these details would be useful in the future, and I'm glad you were able to resolve it. Great catch on the R8, there are also other different Firebase products such as Analytics, Performance which had issues on R8 when Anyhow, since this issue has been resolved, I'll close this for now. Feel free to add any extra details! Thanks! |
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
We rebuilt our app to remove the
android.permission.ACCESS_BACKGROUND_LOCATION
permission.Ever since then, we see the following crash in the Play Console:
Across hundreds of different devices/OS versions/etc.
It's possible that rebuilding the app picked up some updated dependencies somewhere along the way.
No one on our team can reproduce these crashes, across multiple devices/OS versions/etc. Since we can't get a repro, and the crash is in a Google library, we're not sure what steps to take next. We've just been trying different build tool versions, compile SDKs, etc etc.
We don't see the crashes in the Play Console pre-launch. We don't see the crashes on Firebase Test Lab with the following configurations:
Oriole, API Level 31
Pixel 5e, API Level 30
Pixel 4, API Level 29
Pixel 3, API Level 28
Nexus 5, Virtual, API Level 19
Our configuration was (when our app worked without crashes):
Build Tools: 30.0.2
Min SDK: 16
Target SDK: 30
Compile SDK: 30
Dependencies:
We rebuilt the app with the exact same dependencies etc, but it's possible something changed in the dependency tree.
We've since updated all the dependencies to the latest versions, so our build looks like:
Build Tools: 32.0.0
Min SDK: 19
Target SDK: 30
Compile SDK: 31
Dependencies:
We still see the crash in Play Console.
Please... help.
Relevant Code:
The text was updated successfully, but these errors were encountered: