Strange “watched” status issue

General
1

Hello! :slight_smile:

Since the latest update of Infuse, where iCloud syncing has been changed/updated/improved, I am struggling to get watched status’s to stick. I will mark something as watched and within a few seconds it will go back to unmatched. A few seconds after that it will go back to watched. Then, after a random amount of time, it will then go back to unwatched!

I have 4 Apple TV’s around the house (all 4K versions), I have them all linked to the same Library as well as Trakt with Scrobbler on.

Before the iCloud changes, all ATV’s would sync watch status quite happily (after a refresh). Now they all seem to lose sight of the watched status at the same time!

I have deleted the old iCloud (Infuse Pro 6) and kept the new Infuse iCloud entry. If you need more info etc please let me know :slight_smile:

Thanks

1 Like
2

Can you check to ensure you are using Infuse 8.1.6 on all devices and that each device has completed a sync with iCloud?

The initial sync after installing 8.1.6 may take a bit of time but subsequent syncs should be very fast.

3

Hi @james

Yep, all running 8.1.6. All have also synced with iCloud and all on 18.5 tvOS

4

@james

This has just happened to me. A couple things I watched yesterday and something I watched this afternoon are now marked as unwatched.

All my devices are on 8.1.6 and I let all of them sync with iCloud after updating.

In all the years I’ve been using Infuse this is the first time I’m experiencing this issue.

5

Hi @James

Just to say, I’m still having this issue with 8.1.7 but only with TV episodes. Any films I’ve watched seem to keep their watched status.

6

@james It’s happened to me again today. Last night I watched two files: F1’s FP1 and FP2 sessions, both are in the “Other” category. I’ve gone now to watch today’s FP3 session and last night’s FP1 and FP2 sessions were both marked as unwatched.

Edit: Infuse 8.1.7 on ATV.

7

Hi @James

Same issue with 8.1.8 with both tvOS 18.5 and tvOS 26 Development Beta

I thought it had been fixed with 8.1.8 but after a few days it’s started happening again ..