I know this is an old post (which thankfully didn't time out), but this VERY annoying problem persists. Not only are the Custom Channel Logos missing from iOS app but also Smart TV apps (2022 Google TV dongle, and 2023 Google TV Hisense U7).
The Channel Logos DO correctly render on the Guides produced by the Server Web Interface (Docker install), whether accessed on the same machine or another machine on the same LAN. For Safari on iOS, turns out I have too many Channels now for the iOS Safari browser to load Guide page without crashing -- took way too long (including using custom .py scripts and crontab jobs) to set those up to risk altering them for testing purposes.
On the PC, Browser Inspect shows "Broken" Logo relies on localhost in URL:
Broken:
<img src="http://localhost:8092/images/uploads/PawPatrol1.png" loading="lazy" title="KidsTV1" style="max-width: 60%; max-height: 50px; margin-bottom: 5px; filter: drop-shadow(lightgray 1px 1px 1px);" class="">
While working Logo uses hard-coded IP address (which is fine).
Working:
<img src="http://192.168.1.10:8092/images/dizquetv.png" loading="lazy" title="Svengoolie" style="max-width: 60%; max-height: 50px; margin-bottom: 5px; filter: drop-shadow(lightgray 1px 1px 1px);" class="">
I am not aware of any UI trick in the DizqueTV UI that is available to force it to emit real IP address in URL instead of localhost reference. The hard-coded IP is for the default dizquetv.png, which I did change but that covers just one Logo image.
BTW, the Custom Logo files are verified to be there in the ../images/uploads/ folder. (These are copied there by DisqueTV Container, in response to User Input to "Upload" a given Logo image file.) And by "there," I mean a Folder on the Host that is mapped to and available via a Docker Volume defined for the DizqueTV Container.
Although DizqueTV code change could probably solve this problem (by using absolute instead of relative address), the disparate rendering behavior at different Clients (i.e., PC Browser vs. iOS App) suggests perhaps this is best addressed at (or explained by) Channels-dvr team.
Thanks!