erengy / taiga

A lightweight anime tracker for Windows
https://taiga.moe
GNU General Public License v3.0
2.11k stars 229 forks source link

Taiga Client Can't Read My History/Anime List from File Anymore #1221

Open Tom-CSTech opened 6 days ago

Tom-CSTech commented 6 days ago

The file "history.xml" is still full of my history, and "settings.xml" still has my relevant directories listed, but currently the History and Anime List tabs in the app are EMPTY. It suddenly happened a few days ago. I assumed an update broke something, but the last release appears to be March of this year. I use Taiga regularly and this has never happened before. Refreshing, opening and closing, restarting my computer etc. does nothing. What's going on? Why can't Taiga read its own files anymore? I'm scared to watch anything new and update it in case it overwrites the file -- although I already copied them elsewhere just in case. By the way, on the day it happened, I got a Windows notification from Taiga saying that a SPECIFIC show couldn't sync. It's after I closed and reopened the app that it permanently became empty, in spite of still having all the history in the files. image

shyevsa commented 1 day ago

Have you checked the Taiga.log file? sometimes you can find why its not working in there.

for me its often because my Anilist token was expired so I need to reauthorize it. and sometimes its because the cloudflare ddos protection.

also the folder name where the history for me is myanilistname@anilist try checking your service account list and resync or try create new folder with name C:\Users\Username\AppData\Roaming\Taiga\data\user\myanilistname@anilist and place your xml file over there.

Tom-CSTech commented 1 day ago

I'm not sure what originally caused it because after the issue happened, I tried messing with the linked accounts (of which there were none) and it supplemented the title bar, which used to just say "Taiga" as "Taiga - [username]". Then, I found out there was a separate history for the generic, nameless user and for this one that was automatically created when I tried to go to the (non-existent) linked account. So I copied the history from my folder under the nameless user into the folder for this automatically-created one, and Taiga could see that history. So my issue was solved, and technically can be closed... Except it doesn't answer why the original issue happened that forced me to mess around in the first place, which enabled the solution. It worked perfectly fine with no user at all, until randomly one day it didn't. Maybe we care enough about that to keep this issue open, or maybe we don't and it can be closed. I don't really have any other information to help diagnosing it.

Tom-CSTech commented 1 day ago

I'm not sure what originally caused it because after the issue happened, I tried messing with the linked accounts (of which there were none) and it supplemented the title bar, which used to just say "Taiga" as "Taiga - [username]". Then, I found out there was a separate history for the generic, nameless user and for this one that was automatically created when I tried to go to the (non-existent) linked account. So I copied the history from my folder under the nameless user into the folder for this automatically-created one, and Taiga could see that history. So my issue was solved, and technically can be closed... Except it doesn't answer why the original issue happened that forced me to mess around in the first place, which enabled the solution. It worked perfectly fine with no user at all, until randomly one day it didn't. Maybe we care enough about that to keep this issue open, or maybe we don't and it can be closed. I don't really have any other information to help diagnosing it.

Tom-CSTech commented 1 day ago

By the way, the folder for the empty, no-username history is just called "@anilist". With nothing before the "@". Just literally that.

shyevsa commented 1 day ago

well it must be some kind of bug with the service module or the sync. but without reproduceable method its going to be a mystery.

Doomwhite commented 3 hours ago

This has happened to me twice in 4 years.