You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RSS Ticker no longer displays along bottom of Kodi window.
Expected Behavior
Scrolling display of items from RSS feed sources.
Actual Behavior
According to debug log feed URLs are seemingly fetched by Kodi, but fail to display silently with no further log entries until the idle connection is closed after a while.
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
RSS Ticker no longer displays along bottom of Kodi window.
Expected Behavior
Scrolling display of items from RSS feed sources.
Actual Behavior
According to debug log feed URLs are seemingly fetched by Kodi, but fail to display silently with no further log entries until the idle connection is closed after a while.
Possible Fix
Issue seems likely to relate to commit for migration of RSS Ticker functions to tinyxml2:-
https://github.com/xbmc/xbmc/commit/fe6a7b1ed0de937b0b39c7c756dec0ab8c04f6a6
Parent commit for TinyXML2 introduction:-
https://github.com/xbmc/xbmc/commit/9e983ed0449aaf3007d8bfa3261056b120d84188
Commit 9e983ed mentions that "Currently tinyxml2 and 1 can coexist peacefully" - perhaps revert the RSS Ticker files to use tinyxml1 ?
To Reproduce
Steps to reproduce the behavior:
Debuglog
The debuglog can be found here: kodi.log debuglog
Your Environment
Used Operating system:
Android
iOS
tvOS
[*] Linux
macOS
[*] Windows
Windows UWP
Operating system version/name:
Kodi version: 21.0-beta2
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.
The text was updated successfully, but these errors were encountered: