If /profile fetch errors, stream player fails to load.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 46
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Noticed when using a VPN the player window was a blank screen. Figuring maybe that VPN IP was banned I tried opening in a incognito window expecting the same result except... The player loaded as normal.
So going back to the non-incognito tab I checked the network tab and the `/profile` endpoint was returning `403`. I turned off the vpn and got a `200` and the player loaded.
Further testing revealed if I blocked that specific `/api/profile` network call I would get the same blank screen result regardless of VPN/IP.
### Example blocked network call
### Example unblocked network call
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the blank player with the /api/profile request blocked or returning 403, then trace how the player handles that failed request during initialization. Done means the player no longer remains a blank screen when the profile request fails; verify both blocked and successful profile requests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100