SyncTask unregisterReceiver error

[white123483]

[REQUIRED] Step 2: Describe your environment

• Android Studio version: Android Studio Koala | 2024.1.1
• Firebase Component: Messaging
• Component version: 24.1.0

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

I would like to know when com.google.firebase.messaging.SyncTask will be called, because my Google Play console gets task.getContext().unregisterReceiver(this) logging out of the receiver resulting in an error message.

Relevant Code:

// TODO(you): code here to reproduce the problem
Exception java.lang.RuntimeException:
  at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0 (LoadedApk.java:1919)
  at android.app.LoadedApk$ReceiverDispatcher$Args.$r8$lambda$gDuJqgxY6Zb-ifyeubKeivTLAwk (Unknown Source)
  at android.app.LoadedApk$ReceiverDispatcher$Args$$ExternalSyntheticLambda0.run (Unknown Source:2)
  at android.os.Handler.handleCallback (Handler.java:958)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loopOnce (Looper.java:230)
  at android.os.Looper.loop (Looper.java:319)
  at android.app.ActivityThread.main (ActivityThread.java:8919)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:578)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1103)
Caused by java.lang.IllegalArgumentException:
  at android.app.LoadedApk.forgetReceiverDispatcher (LoadedApk.java:1751)
  at android.app.ContextImpl.unregisterReceiver (ContextImpl.java:1933)
  at android.content.ContextWrapper.unregisterReceiver (ContextWrapper.java:837)
  at com.google.firebase.messaging.SyncTask$ConnectivityChangeReceiver.onReceive (SyncTask.java:194)
  at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0 (LoadedApk.java:1911)

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[lehcar09]

Hi @white123483 , thank you for reaching out. From what I can gather, the ConnectivityChangeReceiver is a BroadcastReceiver that listens for network connectivity changes. When a connection is established, it triggers a SyncTask to perform a background synchronization. It then unregisters itself after triggering the task to avoid unnecessary resource usage.

I tried reproducing the issue, however, I did not encounter this RuntimeException. I wonder if it is caused by a race condition.

I’ll raise this to our engineers and create a PR for this issue. Thanks!

[white123483]

你好@white123483，感谢您的联系。据我所知，ConnectivityChangeReceiver 是一个 BroadcastReceiver，用于监听网络连接变化。建立连接后，它会触发 SyncTask 来执行后台同步。触发任务后，它会自行注销，以避免不必要的资源使用。

我尝试重现该问题，但没有遇到此 RuntimeException。我想知道这是否是由竞争条件引起的。

我会向我们的工程师提出这个问题并针对此问题创建 PR。谢谢！

Thank you for your reply! I've tried to reproduce this issue as well, but that didn't work either, so far we only have this error in the Google Play Console crash logs, and more than two hundred users have encountered this issue. So I'm not sure of the exact possible reasons for triggering it

[Heagin-OhJeongSeok]

This issue is also occurring in the firebase SDK for Unity (firebase-messaging-unity:12.1.0).

Could you please tell me when I can expect a fixed SDK?
#6560

This error tends to spike after each update of our game, then gradually decrease.

Firebase Crashlytics logs show that 96% of crashes occurred in the background, and 75% of crashes occurred on Android 15.

Thank you. @lehcar09

[Heagin-OhJeongSeok]

I'm curious about the process for this issue.

#6560
Although the above issue was fixed for the same problem, it doesn't seem to be progressing further in the review stage.

Thank you @welishr

[welishr]

Hi, I'm not sure why a reviewer wasn't assigned for #6560 but for now we believe we should try to better ensure that we're not hitting any error case here rather than catching and ignoring the exception, that way we don't mask any possible true issue bug that may arise.

[Heagin-OhJeongSeok]

Thank you for the revision. I have one more question.

We are using the Firebase Unity SDK, and I’m wondering if an issue fixed in the firebase-android-sdk repository will also be reflected in the Firebase Unity SDK? @welishr