-
Notifications
You must be signed in to change notification settings - Fork 32
Description
Describe the bug
A clear and concise description of what the bug is.
Im using exact same code for different Kick Apps, Some that I made the day the API was launched publicly and 1 I made 2 days ago as well as a buddy made another one yesterday to try.
For the 2 new ones I get to Oauth no problem, come back with everything approved refresh, expire, and access_token, even refreshes in my refresh loop no problems.
The problem is when i goto send a message to chat with that access token, that is valid and refreshed.
this is my response from the send message api call, but if i unlink that bot and go back to my bot that was made day 1 of API it works perfectly all same code. So its gotta be something on the Kick App side?
ERROR - Failed to send message to channel 59637242: 400 - {"data":"Channel not found","message":"Bad request"}
To Reproduce
Steps to reproduce the behavior
- Create a new app
- Try and send message to channel after getting oauth back and storing token of course
Expected behavior
A clear and concise description of what you expected to happen.
- It should use the valid token ive received back and not get errors that arent true, as we are doing the exact same thing with exact same code.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: n/a?
- Browser n/a
- Version n/a
Additional context
Found it pretty weird i made sure i was printing the channel_id i was sending the message to matched the token saved and printing the token all matches up perfectly.
I can use the same code with any other bots that arent freshly made aswell tested same code with 5 different bots now.
So far its only the 2 new ones that were just made in last few days that are messing up, feel like this will be a issue alot for anyone trying to make any app that would off put them since it wont even work anyways.