Thx!
It worked for me. But I still think Infuse should manage this thing in a better way than use an external Trakt progress manager.
Anyway, I saw they are investigating, but, for the moment, thank you.
A Trakt developer told me that they are also aware of issues related to this on their server side. So Iâm not sure if Infuse can resolve it unless they create some workaround if it is actually a trakt.tv server problem. Either way, Iâm glad it helped you & I hope both Firecore and Trakt get onto resolving this.
if this is a Trakt bug, Iâll try turning it off, but I remember it wasnât enough to make it work.
OR⌠Maybe Infuse is not doing âmark as watchedâ correctly on Trakt, causing this issue?
i am developing an APP to track my watching history with other function that TRAKT cannot provide, and i use infuse to watch movies, and i do believe it is the sync btw Infuse and Trakt, in Trakt, it will record where i stopped watching in infuse, but also i can manually mark it as completed in trakt, but it seems to be that it will not go to infuse to mark it as completed. In the meanwhile, if i just mark it as completed in infuse directly, trakt will receive that, it will show double/tribble watch for this movie, but while i reopen infuse, it shows the stop point again, not marked. i do think the problem shall be in infuse rather than trakt, or it is the api info that not synced properly.
The problem recurred for me again with a tv series. Using the GitHub tool I shared earlier resolved it. A bit annoying but at least resolvable.
1 Like
it works for me by using your tool. So you mean it is trakt keeps the progress while we already completed it, thus leads infuse to show the progress? But if that is the case, infuse should compare the time btw the progress record and the completed record from trakt, rather than replying on only progress? But still, it helps me to make infuse looks normal now. But i think the sync with trakt, shall be more careful and smart in next update version.
Quick update.
This issue is related to some recent changes in the Trakt API; specifically, in the methods we use to report playback progress. The pause method has been removed and stop now has a minimum progress requirement.
We have implemented a set of fixes which are currently undergoing internal testing.
Thanks for your patience here. 
5 Likes
still, i have one more question regarding this, in infuse, i watched 90% of one episode, and then i use watching queue to start the next episode. From my idea it is clear that i have completed watching the episode, but in infuse it alwasy keep it as 90% progress. i also tracked in trakt.tv, it shows 90% as well. I have to manually mark this episode as watched in trakt, and then use the github tool to remove 90% progress of trakt, infuse then will show that it is completed. it is really annoied.
You may want to add your support to this suggestion.
With some shows having several minutes of credits and others run credits over the last bit of the show itâs difficult to determine when a video should be considered as watched. Infuse has a pretty good percentage they use and itâs a good mid point for the vast differences among videos.
I had a hard time figuring this one out. I even deleted Infuse on my 2 Macs, 1 iPhone, 1 iPad and 1 Apple TV, plus Infuse iCloud data, then re-installed it on all devices.
Also re-enabled Trakt syncing.
For some TV shows I couldnât have them remain fully watched. Marking episodes or the entire show as watched did not persist.
For an already watched episode of a TV show, if I watch it partially again, then press the âmark as watchedâ button (or the âmark as watchâ button for the entire show, the episode initially appears watched.
But, after quitting and relaunching Infuse, or on other devices, the episode reverts to partially watched.
If I actually watch the end of the episode, it then remains as watched on all devices.
Note that I have trakt syncing and scrobbler enabled on all devices, with a paid (called VIP) trakt account.
Diagnostic code 6XBED
Hello. Any news here? Seems still broken.
Note this thread is tagged as âin progressâ
You can follow the status here.