recloudstream / recloudstream/cloudstream

Old data still present in backup file

Open
#1,161 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Kotlin
Stars
10.7k
Forks
1.1k
Avg merge
1d 23h
Merged PRs (30d)
15

Description

Steps to reproduce

Not sure how to reproduce or if it's still happening.
I've had the same backup file for a long time and i have A LOT of movies and series saved, which I've manually migrated to newer extensions after the old ones stopped working.

Now when i migrated some more movies i noticed that i constantly got asked to replace movies qnd series that weren't even in any watch categories and literally said "none" next to the title
Screenshot_20240628_021958_CloudStream Beta

If i open the backup file in a text editor im able to find titles i don't have saved, from extensions i haven't had installed in a very long time, but im not really sure what im able to remove so would it be possible for you guys to add something that will purge titles that are saved to the category "none" or where the category is missing?

Second problem with old data.

I've changed the download folder twice and for some reason every time i restart cloudstream it re-creates a few empty folders in my old download location of titles that aren't even in the download tab and haven't been for a long time, so I'm not really sure how to remove these from my backup file.

Is there something you guys can do to clear out old downloads that aren't visible in the app?
I have a few downloads but i would happily remove them if it would help getting rid of those "hidden" download entries.

So is this salvageable or am i screwed and have to start over and re-add all movies and series again?

Cloudstream version and commit hash

4.3.2 55a0eb6

Android version

Android 14

Logcat

No response

Other details

No response

Acknowledgements
  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I have updated the app to pre-release version Latest.
  • If related to a provider, I have checked the site and it works, but not the app.
  • I will fill out all of the requested information in this form.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by reproducing the backup and download-folder behavior described for version 4.3.2, then trace how entries with a missing or "none" category and old downloads are retained; done means stale entries can be removed without losing current saved media.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.