-
Notifications
You must be signed in to change notification settings - Fork 6
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
OnContext not called when video component extension is activated #513
Comments
|
Likely related to #284 (or would have the same fix Twitch side) Also do you get differing behaviour when the channel is live/not live? |
|
Both in my case. |
|
Yep, same behavior on our end. The channel being live/not live doesn't make a difference. Only thing that changes is if you deactivate the extension or set it to something other than a video component. |
|
I'm seeing the issue as well. It works after initialization when the theme is changed but can't get the theme when first starting the extension. |
|
Also likely related to #35 Having test this, this morning, I got onContext data if I open, close, and open the extension. |
Brief description
When an extension is just installed, onContext is called, when you activate it on a video component slot. It is not called anymore
Reproduced in viewer / config / dashboard views
How to reproduce
Create an extension with the onContext callback set up, install it, open the config, see the logs from onContext, activate it, refresh the config, no logs anymore
Expected behavior
OnContext should be always called
The text was updated successfully, but these errors were encountered: