As said, if I include that script then anything works and I get the error I mentioned. Is there any reliable example using that script you mention that works? It’s not like the new script doesn’t work for Bits, it just doesn’t work at all – is it meant to be used in local dev with the Developer Rig?
The developer rig does not currently support testing of bits-enabled extensions (in either local mode or online mode). This is something that we are working on though.
I’ll skip the bits functionality for now and I’ll focus on finishing the extension – or I’ll try to implement that part without testing locally, but I have a bad feeling about it
Hi guys, so there is no way to implement and test Bits in extension at the moment?
Isn’t it the only way to monetize extension at the moment? @rbartlet
This way when you call useBits(sku) it’ll skip passing control over to Twitch which would normally open a dialog box to confirm/buy bits/cancel, and instead just call onTransactionComplete.
Also there’s nothing at all stopping you testing Bits outside of the rig by whitelisting a test channel, install the extension on that channel and test there, in which case you will have Twitch’s dialog box, and if the sku is set to being in development it wont actually subtract bits from your account (although you still do need sufficient bits in your account to get a confirm button, otherwise you just get options to cancel or buy bits)
I see, that will be definitely good for testing, thanks.
By the way I’m also missing the way to setup and manage bits products (besides the Manage Products tab within the rig).
Alright, thanks for confirming me that
But will those products setup in the rig work during Hosted Test and Release stages of the extension?
Sorry for all the questions, but I’m finding the Bit implementation process a little tricky.
Yup, ok, I’ll give it a try with setUseLoopback for testing, then setting real products throught the rig and testing them in a whitelisted channel.
Thanks for the help!