Please bear in mind that literally Tom dick harry and his dog just filled his form in… There is gonna be a queue.
I see, it wasn’t very clear if it was a manual process or automatic. I guess early on is when the system will be the most crowded. Maybe better documentation around that would help future people. It also explains why it would get stuck over the weekend.
I’ve now gotten past the process, though I still see value in a sandbox test environment for people to develop and get their feet wet without fully committing with 5 forms and their all their information.
EDIT: I’m starting to use it and this is getting even worst. Before I get to even write and test my first line of code, not only I have to do all that, but I also need to decide on the name of my extension which cannot be changed later… I’m sure you’ll be seeing a lot of “testing123” out there. I’m sorry but this is not how development work. Most people don’t jump into a project with a complete plan, a name, a logo, monetization plans, etc.
When you release copy everything to a key that you use for “real”
So you always have two test apps (one panel one video)
I always test/develop in my “test” keys.
And release into my production keys
Saves faffing too many un/installs as well 
Makes sense. Now that I’m in the system I see there exists a concept of testing. It would definitely be nice if in the future we didn’t have to provide all the extra information and choose a unique name until we go to change from Testing to Released. And I still maintain that all the forms should be filled in parallel and only required for releasing. But yeah the workflow makes sense, and is actually well detailed here: https://dev.twitch.tv/docs/extensions#extension-life-cycle
1 Like