Skip to content

Conversation

@VolkovsaVSA
Copy link
Contributor

Summary

When Kick is launched directly to a specific module using the startScreen parameter, pressing back at the root level now properly closes the Kick window instead of doing nothing.

Problem

When using Kick.launch(context, startScreen) to open a specific module directly (e.g., Control Panel), pressing the back button at the root level did nothing because Decompose's stack navigation doesn't allow the stack to become empty.

Solution

  • Added onCloseRequested callback to RootComponent interface
  • Created CloseAwareStackNavigation wrapper that intercepts pop() calls at root level
  • UI layer sets the close handler via LaunchedEffect in RootContent
  • Added BackHandler support in ControlPanelContent for system back button

Testing

Tested on both Android and iOS - back navigation now correctly closes Kick when launched with startScreen.

bartwell and others added 2 commits December 24, 2025 17:05
When Kick is launched directly to a specific module using startScreen parameter,
pressing back at the root level now properly closes the Kick window instead of
doing nothing.

Changes:
- Add onCloseRequested callback to RootComponent interface
- Create CloseAwareStackNavigation wrapper to intercept pop() at root level
- Set up close handler in RootContent via LaunchedEffect
- Add BackHandler support in ControlPanelContent for system back button
@bartwell bartwell changed the base branch from main to develop January 16, 2026 13:38
@bartwell bartwell self-requested a review January 16, 2026 13:38
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.

2 participants