features.isBitsEnabled false for released version of extension

Extensions
1

Hello Twitch developers community,
I finally got to release a new extension yesterday and was hyped to show it to my viewers. However, I noticed that the bits products are not shown in the extension due to the window.Twitch.ext.features.isBitsEnabled flag being false in the released version. However, in my test version which I also added as a panel for debugging purposes, the same flag is true.

Checking the flag in the browser console for the released version iframe

image

Checking the flag in the browser console for the test version iframe

image

They both have the same title attribute and therefore the frame switcher shows the same exact title but I also verified this behavior by checking the request to my backend in both instances (window.Twitch.ext.features.isBitsEnabled is sent directly to my backend to determine if bits products should be included in the response or not) as well as visually inspecting the response - the released version does not include bits products while the test version does.

Released version does not show the “Racer” category and bits locked products
Request params: /products?bits=false&type=affiliate

image
image617Ă—272 42.4 KB

Test version shows the “Racer” category and bits locked products
Request params: /products?bits=false&type=affiliate

image
image281Ă—141 11.1 KB

I compared the Monetization options of the two versions, they are identical. For testing purposes, I added my test version of the extension in the “Overlay 1” slot where the released version lives just to make sure it isn’t an issue with the slot - the test version still has the flag set to true.

I can’t figure out why the flag is false for the released version and there is no code difference between the two versions at the moment. I did upload the same .zip package for the test version to make sure that this isn’t caused by a bug in my released code that I fixed after submitting to review.

Does anyone have an idea what else I could check or what is going on here? Is there a configuration either for the extension or for my account that I should check? I did not opt out of bits in extensions as e.g. the Soundalerts extension on my profile has a few sounds that can only be played for bits.

Thanks in advance and have a good day,
bamboe

2

did you have the test version installed

Hit release

Then it stopped working?

Full uninstall and reinstall the extension, not deactivate and reactive it.

It’s a long running bug where if the channel has the test version installed and you hit release converting to to the release version, permissions reset/lock off

Related GitHub: Permissions _just don't work_ if a newly release if the test version was installed · Issue #359 · twitchdev/issues · GitHub

1 Like
3

I indeed did! Full uninstall and reinstall did fix the permission issue.

Thanks a lot Barry, you’re a staple in this community and seem to almost always know solutions! Much appreciated. :blush:Also thanks for the link to the GitHub issue, I’ll add that to my template repository to have that in mind in the future.

4

Generally I do all my testing for extensions (bits or otherwise) on my test channel (which is not affiliated) and bypass this code check. (Also means that bits will never be used and when testing I’m always a test user and not the caster

1 Like