feat(logger): [SDK-4835] gate otel-vs-logger switch on SDK_CUSTOM_LOGGING flag

[abdulraqeeb33]

Summary

Replaces the hardcoded LoggerModuleSwitch.USE_LOGGER_MODULE boolean with a remote-config-driven decision so the new multiplatform logger module can be enabled/disabled from the backend instead of via a code change.

• Adds the SDK_CUSTOM_LOGGING feature flag (sdk_custom_logging, FeatureActivationMode.APP_STARTUP).
• LoggerModuleSwitch.useLoggerModule(context) now resolves the flag during early init by reading the cached config straight from SharedPreferences via OtelIdResolver.resolveCustomLoggingEnabled() — before service bootstrap / FeatureManager exist.
• Because the value comes from the config the previous session persisted, toggling the flag remotely takes effect on the next app start, never mid-session (switching observability pipelines mid-run is unsafe).
• Wires the resolver into both call sites: OneSignalImp (lifecycle manager selection) and OneSignalCrashUploaderWrapper (crash uploader selection).

Why read from prefs directly?

The otel-vs-logger choice is made at the very start of init, before the IoC container and FeatureManager are ready. OtelIdResolver already reads other cached values (appId, log level, ids) from prefs on this cold-start path, so the flag resolution follows the same pattern. Matching is case-insensitive to mirror FeatureManager's canonical keys.

Tests

New/updated unit tests (all passing via :OneSignal:core:testDebugUnitTest):

• OtelIdResolverTest — resolveCustomLoggingEnabled(): flag present, case-insensitive, present-among-others, absent, empty array, missing field, no config, null context, invalid JSON.
• LoggerModuleSwitchTest (new) — useLoggerModule() end-to-end: reads cached flag from prefs → true/false, and false when no config.
• FeatureFlagTests — asserts SDK_CUSTOM_LOGGING key + APP_STARTUP activation mode.

Notes

• Base branch is feat/SDK-4835-kmp-logger-module (this stacks on the logger module work).
• An unrelated local gradle.properties publish toggle was intentionally left out of this PR.

Test plan

• CI green (unit tests, detekt, spotless)
• Manually verify enabling sdk_custom_logging remotely routes observability through the logger module on next launch
• Verify default (flag absent) still uses the otel module

Made with Cursor

[github-actions]

📊 Diff Coverage Report

Diff 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

• FeatureFlag.kt: 3/3 touched executable lines (100.0%) (12 touched lines in diff)
• OneSignalCrashUploaderWrapper.kt: 0/1 touched executable lines (0.0%) (1 touched lines in diff)
  • 1 uncovered touched lines in this file
• LoggerModuleSwitch.kt: 0/1 touched executable lines (0.0%) (18 touched lines in diff)
  • 1 uncovered touched lines in this file
• OtelIdResolver.kt: 0/3 touched executable lines (0.0%) (17 touched lines in diff)
  • 3 uncovered touched lines in this file
• OneSignalImp.kt: 0/1 touched executable lines (0.0%) (1 touched lines in diff)
  • 1 uncovered touched lines in this file

Overall (aggregate gate)

3/9 touched executable lines covered (33.3% — requires ≥ 80%)

Per-file detail (informational; gate is aggregate above):

• OneSignalCrashUploaderWrapper.kt: 0.0% (1 uncovered touched lines)

• LoggerModuleSwitch.kt: 0.0% (1 uncovered touched lines)

• OtelIdResolver.kt: 0.0% (3 uncovered touched lines)

• OneSignalImp.kt: 0.0% (1 uncovered touched lines)

❌ Coverage Check Failed

Aggregate coverage on touched lines is 33.3% (minimum 80%).

📥 View workflow run