[Oztechan/CCC#4839] Cancel previous interstitial timer before starting a new one - #4840
Open
mustafaozhan wants to merge 1 commit into
Open
[Oztechan/CCC#4839] Cancel previous interstitial timer before starting a new one#4840mustafaozhan wants to merge 1 commit into
mustafaozhan wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR makes the interstitial ad timer in MainViewModel resilient to a lifecycle quirk where onAppForeground() can be invoked multiple times without an intervening onAppBackground(), preventing multiple timer coroutines from stacking and triggering interstitials too frequently.
Changes:
- Cancel any existing
data.adJobbefore starting a new interstitial timer insetupInterstitialAdTimer(). - Add a regression test verifying that a second
onAppForeground()cancels the previous timer job and leaves only the new one active.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| client/viewmodel/main/src/commonMain/kotlin/com/oztechan/ccc/client/viewmodel/main/MainViewModel.kt | Cancels the previous interstitial timer job before launching a new one to prevent stacked timers. |
| client/viewmodel/main/src/commonTest/kotlin/com/oztechan/ccc/client/viewmodel/main/MainViewModelTest.kt | Adds a regression test ensuring repeated foreground events cancel the prior timer job. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
setupInterstitialAdTimer()now cancels the existingdata.adJobbefore launching a new one.Why
Two
onAppForeground()calls without an interveningonAppBackground()(a lifecycle quirk) would stack multiple timer coroutines, firing interstitials too often.onAppBackground()already cancels the job on the normal path; this makes it robust regardless of lifecycle pairing.Test
Added
onAppForeground twice cancels the previous interstitial timer— asserts the first job is cancelled and only the new one is active after a second foreground (fails on the old code).Closes #4839