Skip to content

fix ani-cli#1656

Closed
ErenYeager01001A wants to merge 1 commit intopystardust:masterfrom
ErenYeager01001A:master
Closed

fix ani-cli#1656
ErenYeager01001A wants to merge 1 commit intopystardust:masterfrom
ErenYeager01001A:master

Conversation

@ErenYeager01001A
Copy link
Copy Markdown

@ErenYeager01001A ErenYeager01001A commented Apr 18, 2026

Problem

ani-cli was returning:
"Specified quality not found, defaulting to best
Episode is released, but no valid sources!"

This was caused by newer responses including a tobeparsed encrypted payload that was not being handled.

Solution

This PR adds support for decoding the tobeparsed field by introducing a decryption step, allowing extraction of valid episode source URLs.

Key Changes

  • Added decode_tobeparsed() function to decrypt AES-256-CTR encoded responses
  • Detects presence of tobeparsed in API response
  • Extracts and decodes source URLs properly

Result

  • Restores working episode links
  • Fixes "no valid sources" error across affected anime

Verification

  • Tested with multiple anime titles
  • Confirmed streams work correctly via mpv

@ErenYeager01001A ErenYeager01001A changed the title Update ani-cli fix ani-cli Apr 18, 2026
@oilmine
Copy link
Copy Markdown

oilmine commented Apr 18, 2026

i have been experiencing this very issue

@nwroblewski
Copy link
Copy Markdown

#1632 - there is change to POST merged and I feel like the PR description is not really accurate since you didn't change the HTTP method in the request rather than added decryption of the response. Please be more accurate now and in the future

@ErenYeager01001A
Copy link
Copy Markdown
Author

#1632 - there is change to POST merged and I feel like the PR description is not really accurate since you didn't change the HTTP method in the request rather than added decryption of the response. Please be more accurate now and in the future

Thanks for pointing this out, I appreciate it.

You're right — the PR description was not accurate. The POST request change was already introduced earlier, and my change actually focuses on handling the tobeparsed encrypted response by adding a decryption step.

I’ll update the PR description to reflect this correctly. Thanks again for the clarification.

@ErenYeager01001A
Copy link
Copy Markdown
Author

i have been experiencing this very issue

Thanks for mentioning this.

I've pushed a fix that handles the tobeparsed response, which should resolve the "no valid sources" issue. Feel free to try it and let me know if it works for you.

@vazqurog
Copy link
Copy Markdown

i have been experiencing this very issue

Thanks for mentioning this.

I've pushed a fix that handles the tobeparsed response, which should resolve the "no valid sources" issue. Feel free to try it and let me know if it works for you.

Had the same issue. its fixed now after installing 4.12

@Derisis13
Copy link
Copy Markdown
Collaborator

Literal duplicate of #1650.

@Derisis13 Derisis13 closed this Apr 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants