You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Attempting to restore an encrypted backup without providing the password / key doesn't result in any useful errors #1052
I have read the FAQ and it doesn't cover the issue.
I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
I'm on the latest version.
I'm not using a test build (alpha/beta/release-candidate).
This issue contains only one bug.
Describe the bug
Reproduction steps:
Install Neo Backup on a fresh installation.
Point it to a previously created encrypted backup directory.
Attempt to restore apps with data.
Actual behaviour:
The restore gets stuck at 0% with status "=d" in the notification.
The app gets restored but not the data.
No logs are emitted about the reason for the failure (at least none that I could find with adb logcat)
Nothing obviously indicates you need to go to Settings --> Service --> Encryption and specify the password / key you set for the backup.
Expected Behavior
The app prompts you for the encryption password / key or at least provides an error in the notification stating that the encryption details were not provided.
Neo Backup's Version
8.3.18
Installation Source
Github/Codeberg/Gitlab releases
Last Known Working Version
N/A
Relevant information
Device: Redmi Note 10 Pro
Android Version: 15
ROM: LineageOS 23.2
First of all, this is obviously a UX issue, not a code functionality bug, feel free to re-classify this as a feature request if you feel it is more appropriate.
However, I personally feel this is probably better classified as a bug considering how unintuitive it is to realize you need to provide the encryption key.
Most people performing a restore probably set up Neo Backup months (possibly years) earlier and may not immediately remember that they set an encryption password / key, especially with the encryption nag having been removed in 8.3.18. I didn't realize that was the actual reason for the failure until I started looking into the actual .properties files, saw the encryption algo / IVs and realized I didn't set a password for decryption anywhere.
Thanks for spending your time on developing and maintaining Neo Backup, putting aside this one minor issue its been a great app.
Activity