Skip to content
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

XC Proxy lose live channel category #111

Open
Olivier6767 opened this issue Feb 19, 2022 · 2 comments
Open

XC Proxy lose live channel category #111

Olivier6767 opened this issue Feb 19, 2022 · 2 comments

Comments

@Olivier6767
Copy link

Hello,
I'm running the latest version from your docker container.
When proxying an IPTV provider using Xtream Code API (not m3U url), I now have the following error:

  • using GSE App (on ios) : application crash hen trying to connect
  • using IPTVX (on ios and AppleTV) : live channels are loading they are all grouped under category 'Other Channels'. The original categories are lost.

When using the same 2 apps with the original IPTV Xstream URL, the channels are grouped correctly in different categories.
When using the same 2 apps with an m3u url to the iptv-proxy, the categories show up correctly.

I've tried this with 2 different IPTV providers, resulting in the same issue.

Thanks.

@Olivier6767
Copy link
Author

Olivier6767 commented Feb 25, 2022

After running multiple tests and debug, I confirm that it works fine for version up to 3.5.0.
Starting with version 3.6.1, the change to FlexInt breaks the following Apps:

  • (ios): GSE IPTV - Xtream Code API - Application crash when connecting to provider
  • (ios): IPTVX - Using Xtream Code API - Categories for Live, VOD and Series are gone, all content is under category 'Other'

Note: Both Apps work fine when connecting to the provider directly.

The crash with GSE IPTV is clearly linked to ServerInfo JSON returning Int instead of String.

Would there be a way to force returning strings instead of Int for the Apps that require this? Maybe with a ocnfiguration switch?

Thanks.

@Tekka90
Copy link

Tekka90 commented May 1, 2022

Hi,
No solution, but I have the same issue as described by Oliver.
I reverted my docker to 3.5 and it is back working...
Nothing is in the log so not sure what is the issue exactly, but if you need more input, I can provide data...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants