Problems with Developer Rig setup

I am having trouble getting the Developer Rig Setup. I’ve followed the steps in the quickstart guide here, set security setting to Developer mode (OS: Windows 10), ran configure.cmd, run.cmd. On yarn start, I am able to compile succesfully, however I get the following CORS error in my console.

Access to XMLHttpRequest at '' from origin '' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I’ve looked through other forum posts surrounding setup issues but they are all dated back to early August and the setup process appears to have changed since the posting of the other issues. Not sure how to get past the above error. Any ideas are much appreciated.

You can ignore that CORS error. It’s just the Twitch Statistics engine failing and is irrelevant to the operation of the Developer RIg.

Are you having another issue?

Thanks for the response! Sorry I should have been a little more specific about what part of the setup I’m stuck on.

When I click on any of the existing example extensions and then click save, nothing happens. I read somewhere that you need to git pull the example and run the extension-init script. I tried doing this with the hello world example extension but couldn’t get that to work either. I’m sure its just that I’m not doing something correctly.

It seems that the documentation is a little lacking around how exactly to get the example extensions setup within the develop rig. Maybe you can point me in the right direction?

You need to populate all the red fields first.

Then you can import an existing project.

Is it required to fill the red form fields in order to create a local extension?

The steps from here, make it sound like I should be able to create a local extension before having to go through setting up the actual extension. Not sure if these steps are out-of-date but they don’t seem to align with what the Developer Rig UI is showing.

Under Choose Extension , check one of the following:

  • Create Local Extension , to use an extension manifest created locally with the rig. Using a local extension manifest is ideal for getting started and experimenting with Extensions.
  • Use Already Created Online Extension , to use an extension manifest already created on your Twitch developer dashboard. Using an extension manifest created on the Twitch dev site enables you to run against production APIs.

The instructions/steps for Creating a “local extension” seem to have gone a wander… You need to use the rig to create a offline manifest file which I don’t recall how to do.

Literally way easier to go make a Extension ClientID and get going

Edit: ah ha: check the PDF

Interesting. It appears the UI is different in the screenshots for this. The steps do make sense for the UI they have a screenshot of in the PDF.

So I guess the question now is, did the UI change since they posted that? Or is my build somehow broken and not displaying UI correctly? If the UI did change, I think requesting that the setup steps be updated would make sense (across github, twitch dev docs, and the pdf)

Thats a good question! It looks like the PDF that we have may be a bit out of date. Our internal teams have been notified and they will be updating it as is necessary. Thank you for pointing this out.

1 Like