8000 Bug when trying to see the EPG of ANY channel · Issue #216 · Fredolx/open-tv · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bug when trying to see the EPG of ANY channel #216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
minterior opened this issue May 15, 2025 · 1 comment
Open

Bug when trying to see the EPG of ANY channel #216

minterior opened this issue May 15, 2025 · 1 comment

Comments

@minterior
Copy link
minterior commented May 15, 2025

Application version:
Open TV v1.5.2 and v1.7.0

How to reproduce:
I right-click on a channel, then I choose the third option EPG.

Error message:
I see a red box on top-right corner with the message:

Missing stream id. Please refresh your sources (Settings -> Refresh All) to enable the EPG feature. Click here for more info

After refreshing all as the message says, the exact same thing happens when clicking EPG.

Here I attach a couple of error messages:

error decoding response body

Caused by:
    invalid type: integer `1747295400`, expected a string at line 1 column 598
error decoding response body

Caused by:
    invalid type: integer `1747281600`, expected a string at line 1 column 258

I know these integers are timestamps:
1747295400 = 2025-05-15T07:50:00.000000+00:00
1747281600 = 2025-05-15T04:00:00.000000+00:00

Also, the pop-up displaying the error message adds:

You may also find detailed logs of what could have caused the errors in $XDG_CACHE_HOME. That corresponds to:
Linux: ~/.cache/open-tv/logs or ~/.var/app/dev.fredol.open-tv/cache/open-tv/logs

Neither of these two paths exists in my computer, and the $XDG_CACHE_HOME variable is empty in both bash and zsh.

I hope this helps.

@Fredolx
Copy link
Owner
Fredolx commented May 16, 2025

This helps a lot, I'll look into it. It should be resolved fast

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

No branches or pull requests

2 participants
0