fix: Activate game container earlier during app pre-launch

[joshuatam]

Description

The container activation was previously happening after setLoadingMessage. This reorders the activation to occur immediately after the container is retrieved, and before clearing session metadata.

This ensures the container is active for all subsequent pre-launch operations, including session management and save file handling, addressing potential timing issues related to the Steam client update.

Recording

None

Type of Change

• Bug fix
• Performance / stability improvement
• Compatibility improvements
• Other (requires prior approval)

Checklist

• If I have access to #code-changes, I have discussed this change there and it has been green-lighted. If I do not have access, I have still provided clear context in this PR. If I skip both, I accept that this change may face delays in review, may not be reviewed at all, or may be closed.
• This change aligns with the current project scope (core functionality, stability, or performance). If not, it has been explicitly approved beforehand.
• I have attached a recording of the change.
• I have read and agree to the contribution guidelines in CONTRIBUTING.md.

---

Summary by cubic

Activate the game container immediately after retrieval during pre-launch. This ensures save downloads and session management run against an active container, avoiding timing issues with the recent Steam client update.

^{Written for commit 03acc2a. Summary will update on new commits.}

Summary by CodeRabbit

• Refactor
  • Optimized the app launch pipeline by reordering container activation to occur earlier in the startup sequence.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6f2eea06-f69b-4422-aeae-e9083e9a39e4

📥 Commits

Reviewing files that changed from the base of the PR and between 60fe979 and 03acc2a.

📒 Files selected for processing (1)

• app/src/main/java/app/gamenative/ui/PluviaMain.kt

---

📝 Walkthrough

Walkthrough

The PR reorders container initialization in the app launch pipeline: containerManager.activateContainer() is now called immediately after container creation instead of later in the sequence after main loading state setup, ensuring the container is active before subsequent download and installation work.

Changes

Container Launch Timing

Layer / File(s)	Summary
Container activation timing adjustment in preLaunchApp app/src/main/java/app/gamenative/ui/PluviaMain.kt	Container activation moved from the post-main-loading-state phase to immediately after container selection, ensuring activation occurs before download/installation work and session metadata clearing.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A container awakes, bright-eyed and early,
No more waiting by the loading state—
It springs to life with purpose surely,
Ready to dance through the launch gate!
Hopping through the pipeline with glee! 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: moving container activation earlier in the pre-launch pipeline, which is the core modification in the changeset.
Description check	✅ Passed	The description covers the key aspects: what changed (activation timing), why (ensure container is active for subsequent operations), and addresses a Steam client update issue. Most template sections are appropriately completed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 1 file