-
Notifications
You must be signed in to change notification settings - Fork 162
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
Restoring Backup Misplaces Custom Tags #872
Comments
Can you show a screenshot with the edit info dialog open, as well as can you try to reproduce it with the next build? |
In other forks, they don't get restored from backups at all. |
I've also come to realize that status was also affected in my backup. Some that should be "Ongoing" got switched to "Completed" -- I regularly have to manually change things to completed, but some are marked Completed in the backup when in the original device/library had it set to Ongoing. Recap: sometimes tags, descriptions, status, etc. are taken from other entries in the backup files of my library. I cannot seem to find a reason why some connect to others and why it happens at random. It only seems to take things from my edits made from an entry, and if edits are made they and their original tags from the source go along with them to another library entry. |
Going to assume this is fixed with the rewrites to backup handlers |
Steps to reproduce
Example:

Phone (original library/device one)
Tablet (library populated by backup)

Expected behavior
The tags should match between the original library and the new library.
Actual behavior
The tags do not always match. I had this issue appear on more than one backup, and the entries having the issue changed each time.
Crash logs
No response
Tachiyomi version
1.9.3 (both devices)
Android version
Android 12 (both devices)
Device
Samsung Galaxy S10 & Samsung Galaxy Tab 6
Other details
I believe this to be an issue with the backup file itself. I don't know enough about the coding of the backup, however through testing that seems to be the main constant in the situation.
Acknowledgements
The text was updated successfully, but these errors were encountered: