-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Disney+ marked as watched not possible #808
Comments
As you suggested on the Kodi forum, I disabled Sync Playback and the option to mark an episode as watched is visible again in the context menu. I'm a bit confused on how this is supposed to work though. What is the function of the Sync Playback option exactly? Is it not bi-directional? It now looks like with the option enabled, you cannot see which episodes you've already watched in Kodi. And with the option disabled, you can see the watched status in Kodi, but it won't be synced back to your Disney+ account? |
It's meant to. But that's broken due to their api changes. There is another
ticket about it somewhere. Even tempted to remove it. It doesn't really fit
into how Kodi works
…On Wed, 24 Jul 2024, 21:35 MauriceW67, ***@***.***> wrote:
As you suggested on the Kodi forum, I disabled Sync Playback and the
option to mark an episode as watched is visible again in the context menu.
I'm a bit confused on how this is supposed to work though. What is the
function of the Sync Playback option exactly? Is it not bi-directional?
It now looks like with the option enabled, you cannot see which episodes
you've already watched in Kodi. And with the option disabled, you can see
the watched status in Kodi, but it won't be synced back to your Disney+
account?
—
Reply to this email directly, view it on GitHub
<#808 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPQAKN5ZOKLM47NWLS6IKLZN5YNVAVCNFSM6AAAAABLLOP5BCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBXGM3TEOBYGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
closing as duplicate of #757 |
The text was updated successfully, but these errors were encountered: