-
Notifications
You must be signed in to change notification settings - Fork 79
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
Error finishing backup: IllegalStateException: No metadata for @pm@ #818
Comments
Thanks for the report! Is there any chance you could mail me the full log to |
Thanks for the quick response! Is there anything I can do to trim down the logs to just the relevant parts? |
A bit of previous content that might be helpful:
|
Thanks, that's helpful already, filtering it to the relevant parts: 12-15 18:59:30.630 1480 19657 V KVBT : Skipping package which was backed up this time: @pm@
12-15 18:59:23.243 1480 19657 D KeyValueBackupTask: Starting key-value backup of @pm@
12-15 18:59:23.257 1480 19657 D KeyValueBackupTask: Invoking agent on @pm@
12-15 18:59:23.260 13691 17233 I BackupCoordinator: Get backup quota for @pm@. Is full backup: false.
12-15 18:59:23.260 13691 17233 I BackupCoordinator: Reported quota of 1073741824 bytes.
12-15 18:59:23.271 13691 13921 D com.stevesoltys.seedvault.BackupMonitor: @pm@ cat: 3 id: 7
12-15 18:59:23.277 13691 13921 I c.s.s.t.b.BackupTransportMonitor: [binder:13691_9 ] sendNoDataChanged(@pm@)
12-15 18:59:23.277 13691 13921 E c.s.s.t.b.BackupTransportMonitor: [binder:13691_9 ] No latest snapshot!
12-15 18:59:23.378 13691 17233 I NotificationBackupObserver: Completed. Target: @pm@, status: 0
12-15 18:59:23.378 13691 17233 I NotificationBackupObserver: 210/247 - System package manager (@pm@)
12-15 19:02:32.865 13691 13957 E c.s.s.r.AppBackupManager: [binder:13691_C ] Error finishing backupjava.lang.IllegalStateException: No metadata for @pm@ So this means that (in the new location) Seedvault doesn't find a previous snapshot, but the system thinks that When changing the backup location, we should have asked to re-initialize the backup, so the system shouldn't think no data has changed. We obviously need to fix this and thanks to your report we can. However, in the meantime, you should be able to work around this issue by disabling app backup and then re-enabling it again. Please let me know if this fixes things. |
Great, yeah that seems to fix it! |
Hi, I'm using Seedvault on Grapheneos, and after switching to the davx5 backend the backup starts failing at the end. I think this is the relevant portion of the log:
The text was updated successfully, but these errors were encountered: