Repository navigation
EasyTV v1.5.2-alpha5
Pre-release
Pre-release
EasyTV v1.5.2~alpha5
Multi-instance sync hardening across the 1.5.2 alpha cycle, plus a fix for blank Browse-view artwork.
Bug Fixes
- Multi-instance sync stays current without a local scan — Shows that gain new episodes on another Kodi instance appear in Browse and random playlists immediately. Shows fully watched elsewhere are removed from the local Browse list. Resume progress refreshes even when the on-deck episode hasn't changed but you've made progress on another device.
- Clone addons now sync via the shared database — Clones (e.g. an "In Progress" clone) connect read-only to the main instance's database for cross-instance state. The main service advertises its DB location so clones don't need their own multi-instance sync setting. Existing clones must be updated — the mandatory clone update prompt will appear automatically.
- Premiere filter respects in-progress episodes from other instances — A show with a resumed E01 (e.g. continuing on another device) is no longer excluded by the "Skip premieres" filter, matching how smart playlists already categorize partially-watched premieres.
- Browse view art no longer latches blank — If the first art fetch in a Kodi session returned an empty or partial result, EasyTV marked the session as "art fetched" and skipped every subsequent fetch, leaving the Browse view with no posters or fanart until the next library scan completed. The session flag is now only set after at least one show's poster is actually populated, and it is cleared at the start of every addon launch so a stale state self-heals on the next open. Reported in #2.
Internal
- Service advertises shared-DB location via window properties; clones use that to bootstrap their connection.
- Stale duplicate database entries are correctly identified and removed during ID-validation rather than triggering a primary-key violation.
- Diagnostic logging added for premiere filter (before/after counts), storage backend selection in clones, and shared-DB sync skip reasons.
- New tests exercise the real pymysql import path and clone-fallback flow without mocking the failing dependency away.