Skip to content
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

Unable to backup successfully since upgrading to the latest version included with GrapheneOS until app data was wiped #869

Closed
prurigro opened this issue Feb 13, 2025 · 1 comment

Comments

@prurigro
Copy link

Unfortunately I won't be able to help debug this as I've already resolved it on my own device, and since I didn't get a clear error it's hard to tell if an existing issue in the tracker covers this (apologies for the noise if it does). I figured it might at least be helpful for someone else who runs into the same thing though, and who knows, maybe it would shine a light on an error that would be quick to solve?

Since GrapheneOS updated to the newer version of seedvault last month, attempts to make backups on top of my existing backup would always end with a notification saying that an error during the backup caused it to fail (no additional information was available when I selected it). Apps individually had a recent backup date, but the "latest backup" was the one I made in December and it was impossible to check the integrity (I could select up to 0B).

Today I decided to wipe the backup and create a fresh one, but I hit the same error. After that I wiped and reset the recovery code and tried again, but hit the same error again. I then ran F3 (fight flash fraud) to make sure the usb wasn't corrupt, re-formatted, reset the recovery code and tried again, but still got the same error.

I was about to give up when I found an issue here that mentioned how GrapheneOS updated seedvault in January, and figured maybe it was old settings or something. So I wiped the seedvault app data + cache, deleted the backup folder again and ran a fresh backup, and this time it finished without error. It even verified the backup after (which I think is new? awesome idea anyway).

Anyway, apologies again if this is noise, and thanks for the great backup solution.

@grote
Copy link
Collaborator

grote commented Feb 13, 2025

This sounds suspiciously like #818

Thanks for reporting! In the future, please export logs from expert settings after an issue occurs.

@grote grote closed this as completed Feb 13, 2025
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

No branches or pull requests

2 participants