Open Roshri opened 8 months ago
Coming from discord
I don't know if it's related but last night, one series that refused to scrobble, finally did it. Kuso Onna ni Sachi Are never scrobbled on it's own before.
I'm trying to locate another issue to reference but essentially what happened to this series before was this:
After fixing the first issue with a Plex Dance, it scrobbled
What happened?
I'm getting lots of scrobble issues.
Most common issue is adding a series to Want to Read is not scrobbling up. This only happens to my user, every other user on my server can scrobble want to read normally. These series have the corresponding Anilist weblink
When this mismatch happens, reading progress on one of these series won't scrobble up since it's already errored out.
Tried doing the whole Force Refresh -> Clear Media Issues and it did scrobble up the reading progress for a few series, but never the "Want to Read" status.
This has been happening for a while already and today I noticed something new. A series showed the scrobble error, but did update on anilist, although it didn't show on my "Activity" page on AL, when searching for the series, it had the correct reading progress
What did you expect?
When a scrobble fails for whatever reason, if I clear the media issues, add weblink and force refresh, I need the "Want to Read" status to be able to add a series to "Plan to Read" on AL
Kavita Version Number - Don't see your version number listed? Then your install is out of date. Please update and see if your issue still persists.
0.7.14 - Stable
What operating system is Kavita being hosted from?
Windows
If the issue is being seen on Desktop, what OS are you running where you see the issue?
Windows
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Firefox
If the issue is being seen on Mobile, what OS are you running where you see the issue?
Android
If the issue is being seen on the UI, what browsers are you seeing the problem on?
Firefox
Relevant log output
No response
Additional Notes
No response