We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Operating system and version: Windows 10 x64 1809
Streamlink Twitch GUI version: 1.7.1
Streamlink version: 1.1
Configuration details: English language
When accessing channel settings for the second time, it doesn't load and shows the following error message instead:
"Attempted to handle event loadedData on <channelSettings:channel_name> while in state root.loaded.created.uncommitted."
"Attempted to handle event
on <channelSettings:channel_name> while in state root.loaded.created.uncommitted."
It affects all channels individually and the application must be restarted to make the channel settings load again.
It should show channel settings like it does the first time we access the channel settings menu.
No log despite using "--loglevel debug".
The text was updated successfully, but these errors were encountered:
7819bd7
Thanks for the bug report!
Sorry, something went wrong.
No branches or pull requests
Bug report
Environment details
Operating system and version: Windows 10 x64 1809
Streamlink Twitch GUI version: 1.7.1
Streamlink version: 1.1
Configuration details: English language
Description
When accessing channel settings for the second time, it doesn't load and shows the following error message instead:
"Attempted to handle event
loadedDataon <channelSettings:channel_name> while in state root.loaded.created.uncommitted."
It affects all channels individually and the application must be restarted to make the channel settings load again.
Expected / Actual behavior
It should show channel settings like it does the first time we access the channel settings menu.
Reproduction steps
Log output
Additional comments, screenshots, etc.
The text was updated successfully, but these errors were encountered: