fix: [SDK-4841] prewarm dispatchers at process start via ActivityLifecycleInitializer#2680
Conversation
Co-authored-by: linear-code[bot] <222613912+linear-code[bot]@users.noreply.github.com>
…x BackgroundManagerTests pollution
📊 Diff Coverage ReportDiff Coverage Report (Changed Lines Only)Gate: aggregate coverage on changed executable lines must be ≥ 80% (JaCoCo line data for lines touched in the diff). Changed Files Coverage
Overall (aggregate gate)1/1 touched executable lines covered (100.0% — requires ≥ 80%) |
? |
Tests seem to run fine on CI. I created this PR on the cloud and it doesn't have JAVA in there. |
Prewarms
OneSignalDispatchersas the first step ofActivityLifecycleInitializer.create(), before activity lifecycle callbacks are registered, so the process-start lifecycle path gets the same dispatcher warmup head start as the other cold-start entry points.Also updates the
prewarm()KDoc entry-point table and adds focused unit coverage verifying the initializer callsprewarm()before lifecycle callback registration while stubbing the real warmup viaIOMockHelper.Verification note: attempted
:OneSignal:core:testOriginalDebugUnitTest --tests 'com.onesignal.core.internal.application.impl.ActivityLifecycleInitializerTests'and:OneSignal:core:detekt, but this sandbox has nojavaonPATHandJAVA_HOMEis unset.