RemoteConfig NullPointerException crash #5751
Comments
|
In my app I also have the same errors, with that version of BoM. Luckily I have a control in the app to prevent that if there are errors in threads other than the main thread, the app does not crash... it is literally saving my life in this case
|
|
Hi there, thanks for the reports. I'm sorry you're running into this. I believe the error is related to a change in BoM version 32.7.3 to proactively close the real-time Remote Config server connection when the app is in the background. (https://firebase.google.com/support/release-notes/android#remote-config_v21-6-2) I haven't been able to reproduce the issue so far, though. If you could, it'd be helpful to see more information about how you're using Remote Config, particularly where in the app you're calling Thanks! |
|
Hello, this is my code. I have not been able to reproduce the error in my tests either. If you need anything else, don't hesitate to ask! The function that is causing the error is the following. Maybe catching any type of exception in the 'catch' is enough to avoid errors. |
|
Thanks for all that info @pacoarjona! That's really helpful. Is |
|
👋 Same issue here. when (isOnline(context)) {
true -> firebase.fetchAndActivate()
false -> firebase.activate()
}
firebase.addOnConfigUpdateListener(
object : ConfigUpdateListener {
override fun onUpdate(configUpdate: ConfigUpdate) {
configUpdate.log()
firebase.activate()
}
override fun onError(error: FirebaseRemoteConfigException) = error.log()
},
)It is called in a |
|
Here's our setup:
|
Hello again! The code is called from the Splash activity of the app, that is, it is called at the start of the app and I have controlled that this code can only be executed once per session. In my case, the error is affecting approximately 7% of the users. 71% (according to crashlytics) of the total were in the background at the time of the error. 2000 errors in approximately 1000 users in just 5 days since I uploaded the update to the Play Store. Here you can see more types of errors in addition to the NPE. Please, in your correction make sure that you capture any type of exception, this is crazy... for now I am going to rollback and put the previous version of BoM while you solve the problem, I cannot continue with so many errors daily. |
|
Thanks again for the reports everyone - we're working on a patch to fix this. We'll update this issue once that's available |
|
Thanks for your patience! BoM version 32.7.4 (Remote Config version 21.6.3) has been released with a fix for this issue: https://firebase.google.com/support/release-notes/android#2024-03-07 |
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:
with the firebase tag.
google group.
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
After upgrading to firebase bom 32.7.3, I'm seeing this remote-config crash on Crashlytics. Mostly when the app is in background, as shown in the screenshot below.
The text was updated successfully, but these errors were encountered: