Skip to content

chore: [SDK-4213] make async init the default in OneSignalImp + startup (part 2/3)#2673

Open
abdulraqeeb33 wants to merge 1 commit into
ar/sdk-4213-part1from
ar/sdk-4213-part2
Open

chore: [SDK-4213] make async init the default in OneSignalImp + startup (part 2/3)#2673
abdulraqeeb33 wants to merge 1 commit into
ar/sdk-4213-part1from
ar/sdk-4213-part2

Conversation

@abdulraqeeb33

Copy link
Copy Markdown
Contributor

Summary

Part 2 of 3 of the SDK-4213 stack. Stacked on #2672 — review/merge after part 1.

Drops feature-flag branching from initialization:

  • OneSignalImp always runs init asynchronously on the dispatcher pool; suspend/blocking wait paths kept consistent.
  • Removes the dead getServiceWithFeatureGate pass-through.
  • StartupService no longer gates on the flag.
  • Updates SDKInitTests, OneSignalImpTests, StartupServiceTests.

Test plan

  • CI green on the full stack (part 3)
  • init/startup unit tests pass

Made with Cursor

…up (part 2/3)

Builds on part 1. Drops the feature-flag branching from initialization:
OneSignalImp now always runs init asynchronously on the dispatcher pool, with
the suspend/blocking wait paths kept consistent, and removes the dead
getServiceWithFeatureGate pass-through. StartupService no longer gates on the
flag. Updates SDKInitTests, OneSignalImpTests, and StartupServiceTests.

Part 2 of 3. Stacked on part 1; merge after part 1.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant