TeamNewPipe / TeamNewPipe/NewPipeExtractor

MediaCCC default kiosk extractor and kiosk list default kiosk don't match

Open
#1,254 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
2k
Forks
602
Avg merge
3d 6h
Merged PRs (30d)
6

Description

Checklist
  • I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
  • I am aware that this issue is being opened for the NewPipe Extractor, NOT the app, and my bug report will be dismissed otherwise.
  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.
Affected version

0.24.2

Steps to reproduce the bug
  1. Get the kiosk list for MediaCCC with getKioskList and receive a default kiosk via getDefaultKioskId.
  2. Get a default kiosk extractor for MediaCCC with getDefaultKioskExtractor
  3. Notice these don't match: 1 returns "recent" while 2 returns "conferences" for the extractor ID but returns related streams for the "recent" extractor
Expected behavior

The default kiosk should match in both cases for MediaCCC.

Actual behavior

You can try this by going to https://api.tubo.media/api-docs, executing the request with ID 2 for MediaCCC for /api/v1/services/{service-id}/default-kiosk and then executing the request for /api/v1/services/{service-id}/kiosks and you'll see the disparities in the results.

Screenshots/Screen recordings

No response

Logs

No response

Additional information

No response

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

Start by tracing MediaCCC's getKioskList, getDefaultKioskId, and getDefaultKioskExtractor implementations and compare the kiosk IDs and returned streams. Reproduce the discrepancy using the default-kiosk and kiosks requests in the linked API documentation. Done means both default-kiosk paths identify the same MediaCCC kiosk and return consistent results.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.