[Bug]: java.util.concurrent.RejectedExecutionException

[rw-exxeta]

What happened?

We received two crash reports regarding this exception. I see you already fixed a crash related to this exception, however this might be another place where the crash can happen, but it's pretty rare, but worth to have a look. https://github.com/OneSignal/OneSignal-Android-SDK/issues/669

Steps to reproduce?

we received the crash report, sadly we couldn't reproduce it.

What did you expect to happen?

the app doesn't crash

OneSignal Android SDK version

Release 4.8.4

Android version

13

Specific Android models

* Samsung Galaxy Note20 Ultra 5G (SM-N986B)
* Samsung Galaxy S20 (SM-G980F)

Relevant log output

java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@f6db105[Not completed] rejected from java.util.concurrent.ThreadPoolExecutor@c82155a[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 2]
	 at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2072)
	 at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:834)
	 at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1364)
	 at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
	 at java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:671)
	 at com.onesignal.OSTaskController.startPendingTasks(OSTaskController.java:65)
	 at com.onesignal.OneSignal.init(OneSignal.java:164)
	 at com.onesignal.OneSignal.setAppId(OneSignal.java:87)
	 at com.onesignal.OneSignal.reassignDelayedInitParams(OneSignal.java:61)
	 at com.onesignal.OneSignal.onRemoteParamSet(OneSignal.java:0)
	 at com.onesignal.OneSignal$7.complete(OneSignal.java:29)
	 at com.onesignal.OneSignalRemoteParams.processJson(OneSignalRemoteParams.java:10)
	 at com.onesignal.OneSignalRemoteParams.access$100(OneSignalRemoteParams.java:0)
	 at com.onesignal.OneSignalRemoteParams$1.onSuccess(OneSignalRemoteParams.java:2)
	 at com.onesignal.OneSignalRestClient$5.run(OneSignalRestClient.java:4)
	 at java.lang.Thread.run(Thread.java:1012)

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[brismithers]

Looks like this line here.

Note this is not an issue in v5.0.0 which is currently in beta. Marking as a bug and to determine whether to fix in 4.x releases.

[shefich]

I think I have the same issue:

Non-fatal Exception: java.lang.Exception
AndroidJavaException : java.lang.NullPointerException
java.util.concurrent.AbstractExecutorService.submit (java.util.concurrent.AbstractExecutorService)
java.util.concurrent.Executors$DelegatedExecutorService.submit (java.util.concurrent.Executors$DelegatedExecutorService)
com.onesignal.OSTaskController.startPendingTasks (com.onesignal.OSTaskController)
com.onesignal.OneSignal.init (com.onesignal.OneSignal)
com.onesignal.OneSignal.setAppId (com.onesignal.OneSignal)
com.onesignal.OneSignal.reassignDelayedInitParams (com.onesignal.OneSignal)
com.onesignal.OneSignal.provideUserConsent (com.onesignal.OneSignal)
com.unity3d.player.UnityPlayer.nativeRender (com.unity3d.player.UnityPlayer)
com.unity3d.player.UnityPlayer.access$300 (com.unity3d.player.UnityPlayer)
com.unity3d.player.UnityPlayer$e$1.handleMessage (com.unity3d.player.UnityPlayer$e$1)
android.os.Handler.dispatchMessage (android.os.Handler)
android.os.Looper.loopOnce (android.os.Looper)
android.os.Looper.loop (android.os.Looper)
com.unity3d.player.UnityPlayer$e.run (com.unity3d.player.UnityPlayer$e)
UnityEngine.AndroidJNISafe.CheckException (UnityEngine.AndroidJNISafe)
UnityEngine.AndroidJavaObject._CallStatic (UnityEngine.AndroidJavaObject)
OneSignalSDK.OneSignalAndroid.set_PrivacyConsent (OneSignalSDK.OneSignalAndroid)
OneSignalInit.ReceivedUserConsent (OneSignalInit)
Hyperbyte.ConsentSetting.OnContinueButtonPressed (Hyperbyte.ConsentSetting)
UnityEngine.Events.UnityAction.Invoke (UnityEngine.Events.UnityAction)
UnityEngine.Events.UnityEvent.Invoke (UnityEngine.Events.UnityEvent)
UnityEngine.EventSystems.ExecuteEvents+EventFunction`1[T1].Invoke (UnityEngine.EventSystems.ExecuteEvents+EventFunction`1[T1])
UnityEngine.EventSystems.ExecuteEvents.Execute[T] (UnityEngine.EventSystems.ExecuteEvents)
UnityEngine.EventSystems.StandaloneInputModule.ProcessTouchPress (UnityEngine.EventSystems.StandaloneInputModule)
UnityEngine.EventSystems.StandaloneInputModule.ProcessTouchEvents (UnityEngine.EventSystems.StandaloneInputModule)
UnityEngine.EventSystems.StandaloneInputModule.Process (UnityEngine.EventSystems.StandaloneInputModule)
UnityEngine.EventSystems.StandaloneInputModule:Process (UnityEngine.EventSystems)

Unity 2020.3.47f1 (64-bit) OneSignal 3.0.10

[mrRedSun]

I received the same issue in Crashlytics, but haven't been able to reproduce it.

[jennantilla]

Hello everyone! Apologies that this issue has gone stale. Much of our work in the last few quarters have been on a new major release where many improvements and enhancements are introduced. We will continue to investigate 4.x.x bugs, though we encourage you to update to our latest release as that will be the most-supported release going forward. Please see our migration guide for full details on upgrading.

If this crash is still a current concern, please let us know and we will investigate further.