recloudstream / recloudstream/cloudstream

Source prioritizing doesn't work on first start on aniyomi extensions

Open
#1,114 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

On aniyomi extensions you have to setup every resolution for every single source instead of just setting up resolutions and sources separately.

  1. Set up your source prioritization, anime extensions in my case with dubs on top and subs below.
  2. Go back to the shows title page and start a new episode, not one you've already played since restarting the app

I mostly use kaido and hianime but they're probably not the only ones

Expected behavior

Expecting the episode to always play the highest prioritized source, dubs in my case.

Actual behavior

First time you start an episode it will start in sub, if i go back and start it again it will correct itself and play the correct source from there on.
If i go back to the title page and start any other episode that haven't been played since the app was started, the same thing will happen, but if i let it play till the end and use the "next episode" button it will always start with the correct prioritization.
And all episodes will go back to starting incorrectly after restarting the app.

Cloudstream version and commit hash

4.3.2 b3e3dad

Android version

Android 11

Logcat

No response

Other details

It's been happening for maybe a week or so, can't say exactly when it started

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 first-episode behavior after an app restart with source prioritization configured, then trace the source-prioritization and episode-start paths; done means new episodes consistently select the highest-priority source without requiring a second launch.

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
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.