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

Older backup might be automatically suggested to restore account data #2111

Closed
gerryfrancis opened this issue Nov 3, 2021 · 3 comments
Closed
Labels
enhancement actually in development, user visible enhancement

Comments

@gerryfrancis
Copy link
Contributor

gerryfrancis commented Nov 3, 2021

  • Android version:
    Android 11.

  • Device:
    Fairphone FP2 (Lineage OS 18.1 build RQ3A.210705.001 from 2021-10-29).

  • Delta Chat version:
    1.23.0 (latest nightly build).

  • Expected behavior:
    Delta Chat always suggests the latest backup available to restore account data.

  • Actual behavior:
    Delta Chat not always suggests the latest backup available to restore account data.

  • Steps to reproduce the problem:
    -- Perform two backups on the same day (e.g. today), one after another ("Settings" -> "Chats and Media" -> "Back Up Chats to External Storage" -> "Start Backup"), and wait until the processes have finished. (The file names could be like these: delta-chat-backup-2021-11-03-00.tar (1st backup), and delta-chat-backup-2021-11-03-01.tar (2nd backup).)
    -- Open the "Files" (or another equivalent) app, and locate the backup files in the Download folder.
    -- Delete the file delta-chat-backup-2021-11-03-00.tar, or rename its file name.
    -- Perform another backup on the same day. (Result: The name of the first file - its name ending with 00.tar - will be applied to the backup file.)
    When account data must be restored later on, Delta Chat generally interprets *01.tar to be a younger backup file than *00.tar, but that can be wrong obviously...

  • Screenshots:
    N/A.

  • Logs:
    N/A.

@adbenitez adbenitez added the enhancement actually in development, user visible enhancement label Mar 27, 2022
@adbenitez
Copy link
Member

that is something expected if you rename backups, at some point would be better to let manually select backup file I guess

@r10s
Copy link
Member

r10s commented Mar 14, 2023

closing stale issue, i also think, the current behaviour is reasonable. if needed, we can open a request in the forum.

also, with #2493 backups will become less important, so that this situation will be even more rare.

@r10s r10s closed this as completed Mar 14, 2023
@gerryfrancis
Copy link
Contributor Author

@r10s @adbenitez Sorry, I totally forgot about this one! Now that we are able to select any backup file, this issue is no longer valid anyway. Thank you for closing! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement actually in development, user visible enhancement
Projects
None yet
Development

No branches or pull requests

3 participants