Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Feature Request: Repair / Migrate Library Items From Broken Extensions

Aperta
  • Qualcosa non va?
#3,146 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, kotlin
Ambito
mobile

Direzione di ricerca

Parti da Settings → Library e traccia il flusso esistente di duplicazione/sostituzione della libreria, il comportamento di ricerca del provider e la logica di corrispondenza titolo/anno/tipo descritta nell’issue. Il lavoro è completo quando le voci non funzionanti possono essere scansionate, associate a estensioni funzionanti, esaminate dall’utente e migrate mantenendo cartelle, stato e informazioni di monitoraggio.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
Describe your suggested feature

Please add a Library repair/migration tool that allows users to move saved movies and shows from extensions that are no longer working to currently installed and working extensions.

CloudStream already appears to have similar matching logic when adding a movie or show that is already present in the Library from another extension. When this happens, CloudStream recognizes that the two entries appear to represent the same title and asks whether the user wants to replace the existing entry or keep both.

It would be very useful to expose similar functionality as a Library maintenance tool.

For example:

Settings → Library → Repair / Migrate Library

The tool could:

  1. Scan Library entries and identify items whose original extension/provider is no longer installed or no longer works.

  2. Allow the user to select one or more currently enabled extensions to use as replacement sources.

  3. Search those extensions for each broken Library item using the existing title/year/type search logic.

  4. Detect likely matches using the same or similar matching logic that CloudStream already uses when duplicate Library entries are added.

  5. Show the user the proposed replacement and allow:
    Replace
    Skip
    Choose another result

  6. Preserve the existing Library folder/status and watch information when replacing the provider.

An optional feature could automatically replace very high-confidence matches while asking the user to review uncertain matches.

Other details

This request came from a problem I recently ran into myself. I took a break over the summer from watching many movies, and when I started using CloudStream regularly again, I discovered that the main extension I had used for most of my Library had gone down.

As a result, a large portion of my Library is now essentially a wall of gray squares. The Library entries are still there, but the artwork and links associated with the old extension are broken.

I spent some time discussing the problem with AI and looking at different ways I might repair or migrate the Library manually. From what I could determine, there does not seem to be an easy way to automatically transfer those existing Library entries to a working extension. The current solution appears to be searching for each movie or show individually through another extension, adding it again, and then using CloudStream's existing duplicate/replacement prompt. That seems workable for a few titles, but it becomes very tedious for a larger Library.

That discussion is what led to this feature request. From a user-facing perspective, CloudStream already appears to have several pieces of functionality that seem related to this problem: searching for the same title across other extensions, recognizing when two Library entries appear to represent the same movie or show, and offering to replace an existing entry when a duplicate is added. My thought was whether those existing behaviors could somehow be combined into a Library repair or migration tool.

I want to acknowledge that I do not have a deep understanding of CloudStream's codebase or how these features are implemented internally. This suggestion is based mainly on observing how the existing features behave from the user side. I do not know whether the duplicate detection, cross-extension searching, Library storage, and provider data are actually connected in a way that would make this relatively straightforward, or whether implementing something like this would require a significant amount of new work under the hood.

So I am not assuming this is an easy feature to implement. The main idea is simply that, from the user's perspective, much of the manual workflow already seems to exist in separate parts of the app, and having a tool that helps apply that workflow across broken Library entries could make recovering from a discontinued extension much easier.

Acknowledgements
  • My suggestion is NOT about adding a new provider
  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
Lingua principale
Kotlin
Stelle
11.1k
Fork
1.2k
Merge medio
3g 18h
PR unite (30g)
12

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di recloudstream/cloudstream

Tutte le issue di recloudstream/cloudstream

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.