-
Notifications
You must be signed in to change notification settings - Fork 80
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
cannot debug backup error #859
Comments
the error occurs when the progress bar in the "Backup running" notification reaches 100%. here is a video: |
try disable app backups and enable it again. if that doesn't work, please send me the full log file. A non-developer can't extract meaningful excerpts. if anything, grepping for Exception has a higher chance to uncover a first clue. |
This comment has been minimized.
This comment has been minimized.
@dmark04 did you try this? |
I have. no effect. same useless error message. I can also send some logs if that helps? |
I had this problem as well. I did many things like clearing Seedvault app data, turning off/on backup, turning off apk backup in expert settings, reentering my passcode in verify code and maybe some more stuff I do not remember. After doing all this I was able to make backups work again. I will have to fix this on other devices which are upgraded to LineageOS 22.1. I will note the steps I have to do to make backups work again and share them here. Also @grote I have some log files I saved after this happened, I can send to you privately as I do not want my private information to leak from them and I might remove useful information from them by trying to remove this information from them. Edited: Corrected wording. |
i did this before:
which means it did all the APK backups again. re-initializing the backup location seems to be more than just turning off and on. if you still want me to do that, i'll do it when i'm home.
sure thing. how do i contact you privately? |
logs can be send to |
What I received in the mail so far is #818 which will get fixed by #845. People who built their own ROM can please pull this in and see if it fixes the issue. However, as a workaround, disabling and then enabling app backup should fix it as long as the first backup run after that can run through without (network) errors. |
I will try this on other device which cannot backup after upgrading but I think I will probably have to do what I did on my main device to make it work. |
thank you! i confirm i have the same issue, as evidenced by the issue being fixed by toggling backup off and on, so no need to send you email. please close this issue at your convenience, thanks again. |
today backups are back to the old behavior of just failing. at some point i'll upgrade my build of the OS and see if that helps. i'd really loved it if there was a way to upgrade the app independently of the OS, as is for microG for example, where the prebuilt is preinstalled in custom OSes and updates are distributed via an f-droid repo, all signed by the microG project. beyond it needed to be installed as a system app, is there any reason why this app couldn't be prebuilt? |
can you send me the log exported right after it the backup fails?
you can just build the APK of the app, sign it and install it manually, no problem with that, just take care to sign with right (platform) key and that the user-installed system-apk takes precedence over the system one, so you may need to uninstall the "upgrade" if you move to system ROm only APKs. |
log sent by email thanks! |
Something wrong with the backup location: 02-10 19:06:00.437 4892 11360 W DocumentsContract: Failed to create document
02-10 19:06:00.437 4892 11360 W DocumentsContract: android.os.ParcelableException: java.io.FileNotFoundException: Failed to upload document with path /.SeedVaultAndroidBackup/191d5b2d36c86db7801b6296dfacfcdb7a8b467203fc17230c074617ffe7b997/88/8875979cfe302b3359e4144dc23f18b917f83cedc0adca118924f6cc09a26289
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.os.ParcelableException$1.createFromParcel(ParcelableException.java:82)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.os.ParcelableException$1.createFromParcel(ParcelableException.java:79)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.os.Parcel.readParcelableInternal(Parcel.java:5064)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.os.Parcel.readParcelable(Parcel.java:5046)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.os.Parcel.createExceptionOrNull(Parcel.java:3226)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.os.Parcel.createException(Parcel.java:3215)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.os.Parcel.readException(Parcel.java:3198)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:203)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:155)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.content.ContentProviderProxy.call(ContentProviderNative.java:764)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.content.ContentResolver.call(ContentResolver.java:2466)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at android.provider.DocumentsContract.createDocument(DocumentsContract.java:1380)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at androidx.documentfile.provider.TreeDocumentFile.createFile(TreeDocumentFile.java:54)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at androidx.documentfile.provider.TreeDocumentFile.createFile(TreeDocumentFile.java:46)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at org.calyxos.seedvault.core.backends.saf.SafHelperKt.createFileOrThrow(SafHelper.kt:67)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at org.calyxos.seedvault.core.backends.saf.SafHelperKt.getOrCreateFile(SafHelper.kt:51)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at org.calyxos.seedvault.core.backends.saf.SafHelperKt$getOrCreateFile$1.invokeSuspend(Unknown Source:13)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:32)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:280)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:85)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source:1)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source:1)
02-10 19:06:00.437 4892 11360 W DocumentsContract: at com.stevesoltys.seedvault.transport.ConfigurableBackupTransport.finishBackup(ConfigurableBackupTransport.kt:138) So the SAF API only logs: You said that you are using Nextcloud. How do you connect Seedvault to it? The Nextcloud app, DavX5 or native WebDAV support? |
sorry, due to a misconfiguration, i was using the nextcloud app 3.31.0 RC1. i downgraded to 3.30.8 (without clearing settings) which worked, but after that i had to reconnect seedvault anyway. but i backed up and it failed at the end again. never mind this unsupported config. i think seedvault worked before RC1 was installed. i will reset the storage in nextcloud, reconnect the storage, and backup, and i guess it will work again. sorry to have wasted your time. |
i confirm that backups now worked, i made several. thanks again. |
im a little stuck...
im running self-built lineageos 4 microg 22.1 with seedvault 15-5.2 backing up to my up-to-date nextcloud.
i was running self-built android 14 and backups worked fine. then i upgraded to self-built android 15 and i started getting backup errors. there is a non-descriptive notification:
i tried removing the backup dir in my nextcloud and re-initializing the backup location, but nothing changed.
i back up only selected apps. some backed up, other did not. while backing up, i can see that the progress notification shows some APKs are being backed up which i didn't choose to backup, and i don't know why.
i saved the backup log. here are some excerpts:
how do i go about understanding what is going wrong here?
The text was updated successfully, but these errors were encountered: