Torsten Grote

Related: https://github.com/seedvault-app/seedvault/issues/405

Make sure Seedvault is using that old backup currently (like by doing a restore without any apps) and then use the auto-restore feature to get the app data restored when...

Some behavior changes to check: * [x] Apps need to ask permission to show notifications - https://developer.android.com/about/versions/13/changes/notification-permission * [ ] New rules for intent filters could affect our use of...

* There's an [`EncryptedLocalTransport`](https://android.googlesource.com/platform/frameworks/base.git/+/android-13.0.0_r3/packages/EncryptedLocalTransport) now. Not sure if functional. * But looks like the "Encryption in the Framework project" [is dead](https://android.googlesource.com/platform/frameworks/base.git/+/5169896db8741a7d1cadefb3616d8f1ed604fef6)? * timeout in `TransportStatusCallback` was [halfed to 5min](https://android.googlesource.com/platform/frameworks/base.git/+/3f82689d2b59f1437479ccb3fb69e662a98ac2fb%5E%21/#F1) which...

more verbose log when I reproduced this by backup up and then restoring and then doing another backup: ```ruby 2022-09-08 16:44:58.517 9670-9696/com.stevesoltys.seedvault I/PackageService: Got 241 packages: 2022-09-08 16:44:58.807 9670-9696/com.stevesoltys.seedvault I/PackageService:...

What I find curious: ```ruby I/KeyValueBackupTask: Initializing transport and resetting backup state I/PMBA: Previous metadata null mismatch vs eng.cdesai.20220908.170828 - rewriting ``` Now this could be due to restoring mid-flight...

So it seems to be actually us returning `TRANSPORT_ERROR` (aka `-1000`) to the system, but we fail to log the reason for it. > When @pm@ comes back with status...

We pre-grant the notification permission now and if the user removes it, there's no crash or anything, so I guess nothing else to do about it. In settings, there's new...

Does it still happen after turning Backup my apps on and off again?

Can you try re-setting your backup location? It is on a flash drive, right? If that doesn't help, please provide logs when doing this resetting and ideally right after you...