Repository navigation
Fix playback stopping when Android backs up the app #6205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+9
−1
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
48c1f06
Fix playback stopping with a full backup
geekygecko 5e2fad1
Add CHANGELOG entry for the backup playback fix
geekygecko 4b39ccb
Improve the changelog
geekygecko fdba244
Merge branch 'main' into philip/backup-playback
sztomek ee288aa
Remove the backupInForeground attribute
geekygecko File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On Android 16+, a user restoring to a new phone can end up with their restored podcasts and settings overwritten or reset, because restore now runs inside the full app process.
This property turns off restricted mode for restore as well as backup. That means
PocketCastsApplication.onCreateruns first: Hilt init, Room opening and migratingpocketcasts, andSettingsloadingau.com.shiftyjelly.pocketcasts_preferences.xmlinto theSharedPreferencescache. Then the transport replaces those files underneath it. Because the process is no longer killed on unbind (theshouldKillAppOnUnbindpath you cite), it keeps running with an open Room connection to the old file and a stale prefs cache. The nextapply()writes the pre-restore prefs back over the restored file, and DB writes go to the replaced inode. Step 6 of the test plan probably won't catch this, because the restore usually runs before anything in the app touches prefs or the DB.Fix: keep the backup benefit but make restore safe. Add a minimal
android:backupAgentwithandroid:fullBackupOnly="true"(it stays a full backup with the same rules) and end the process inonRestoreFinished()(exitProcess(0)) so the next launch reads the restored files. Then test restore with the app already running, e.g.bmgr restore <token> au.com.shiftyjelly.pocketcastswhile it's in the foreground.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I completed the restore successfully in my testing, and everything worked as expected.