Skip to content
Translate Ideas and Comments
Choose language:
There was an error during translation

Developers

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

171 results found

  1. Provide a link to the referenced branch associated with each step.

    There are no branches for steps 3 and 4. The existing branches don't correlate to the code presented for each step on this page.
    And there's messy commented out code in all of the files on GitHub.

    Also, 4 steps are explained, and then the last sentence in this doc mentions the Step 1 branch

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. I received an error I have never seen before and it got me thinking it would be nice to have some documentation on various error messages like "Insufficient authorization in token". Other errors are clear and straight forwards like "missing X scope" however some are vague and unclear.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. The hub.secret property needs far more explaining of how the secret is generated:

    "The X-Hub-Signature header is generated by sha256(secret, notification_bytes)"

    It should say something along the lines of

    "The X-Hub-Signature header is generated by using HMAC sha256 with the provided secret being the one specified in hub.secret: hmac(sha256, hubsecret).hash(notificationbody)"

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. https://imgur.com/a/kBcNDeh

    The use of bullet points reads and the "and" tacked onto the end of the first bullet point makes it unclear

    The wording should be revised so it's more obvious that "onTransactionComplete" is to be sent to instances where the userID matches the userID that initiated.

    Since the first bullet point is superflous, since the userID of the first bullet point is also matched by the second bullet point.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Please add actual code instead of images in the documentation. It would be much easier to copy it. Example: https://dev.twitch.tv/docs/tutorials/extension-101-tutorial-series/config-service

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Hey, it says "/vip /unvip" is under "channel:moderate" scope, wouldn't that be moderator status? because I'm sure moderators can't grant/remove VIP status to a user. Or am I wrong?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. https://dev.twitch.tv/docs/authentication

    Says

    Authentication involves:
    
    Registering your app to obtain a client ID and client secret.
    Getting a token. This includes specifying scopes, the permissions your app requires.
    Sending the token in your API request, to authenticate API requests.
    
    

    But doesn't mention that an Extension is also an Application

    This docs fix would be needed on other pages where "registering an app" is mentioned

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. https://dev.twitch.tv/docs/extensions/reference#helper-viewer

    SNIPPET STARTS

    onChanged
    Twitch.ext.viewer.onChanged: void function(callback: Function())

    This function binds a callback will be invoked when the viewer’s status changes (e.g. if a viewer subscribes and changes their subscription status).

    SNIPPET ENDS

    Cannot tell if broken or only triggers on subscription status change.

    IE is it supposed to trigger on role changes? If so it's bugged, if not the documentation needs to document what does cause onChanged to be called

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Pagination Support
    None.
    There is a limit of only 50 Custom Rewards on a channel at a time.

    It's unclear if that means 50 active rewards or 50 total rewards. It should be more plain text/clear.

    The help article

    https://help.twitch.tv/s/article/making-the-most-of-channel-points?language=en_US

    doesn't mentioned this limit either.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. This is out of date. Update it please.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Description in "Getting tokens" isn't very clear and missing a link to "Getting Tokens: OAuth", where it's all explained in detail. That does confuse people

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. This page seems extremely out of date and the example deep links given don't work on tvOS.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. It would be great if we could have a list of the status codes and their reasons so we can write code to prepare for handling those errors, instead of logging them and dealing with them as they happen - for all endpoints. These exist, for the most part, in a lot of the newer endpoint documentation, but a lot of the older endpoints were rushed in their documentation and we have little information on what responses to expect. Sometimes we get 200s, 202s, 400s, 410s - and having to just "wait" or try to plan for them is a…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. The step by step guide does not reference OAuth tokens yet they are required to do an API request, please update the guide to include info on this.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. More information is required about the uniqueness of id. Is it unique forever (i.e. there will never be two messages with the same id) or is it just guaranteed unique within a timeframe?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. msgid:"usageuntimeout" states:'Usage: “/raid <username>” - Removes a timeout on a user.' and not /untimeout

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Another way to manage an extension secret is to use a .env file. The .env file can be used to store all kinds of secrets, tokens, and passwords.

    eg: TOKEN=testT0K3N

    note: .env is a shell file so there can't be spaces around =

    Page: https://dev.twitch.tv/docs/extensions/building

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. The formatting of the link to the locustfile in https://dev.twitch.tv/docs/extensions/load-testing-extensions#run-your-locust-test is not working because there are code tags in front of and after:

    locustfile.py

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Build your first Extension
    Here’s an extension that just says ‘Hello, world!’

    where do i store this? how do i connect this with the twitch extension config page?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?