JoselleAstrid
commented
7 years ago I noticed the same thing for GET /videos/followed. Seems like it started happening 1-2 weeks ago.
Open Netflyerr opened 7 years ago
JoselleAstrid
commented
7 years ago I noticed the same thing for GET /videos/followed. Seems like it started happening 1-2 weeks ago.
I developed an app over a year ago and the app was thoroughly tested and everything worked until recently. All my requestes specify version and oauth token (although I know I don't need to specify cliente ID when using oauth token I have tried adding the cliente ID to see if these unexpected results would stop). I thought the version is used precisely to avoid apps from breaking unexpectedly!
A few of the unexpected responses since recent are:
When calling the end point:
DELETE /users/:user/follows/channels/:target returns a 204 no content. I'm almost sure that before it returned something other than a 204 (using the twitch SDK which uses JSONP) response because my app wouldn't hit the failed chained method when calling $ajax call. If I use JSON it works and doesn't fail.
I tested another feature of my app. A request from:
GET /videos/followed
Now returns "{"error":"Bad Request","status":400,"message":"400: Invalid value for broadcast_type: "}"
Invalided broadcast_type??? This is an optional parameter from the documentation, only when adding the parameter does the end point return the data. It worked before without using the parameter, which is what is expected, after reading the documentation and it used to work.
More unexpected behavior is coming from:
GET /users/:user/follows/channels/:target
When checking if a user (x) follows another user (y) if user (x) follows user (y) everything works as before, but if user (x) doesn't follow user (y) then the end point returns a 404! I don't think this was the response before, because as I have said my app worked perfectly and wouldn't call the failed method as it does now.
So what is up? Why is this happening? I haven't migrated to version 5 yet, but version 3 is supposed to work until the beginning of 2018 (in a deprecated state, but working 100%), right?
To reinforce what I have said my app worked 100% for over a year!
I hope these issues are taken under consideration and are fixed, or documented.
Thank you very much!