Closed faroukbmiled closed 2 months ago
Nevermind the issue was unrelated to the token itself Issue was i was using the old "client.user.id" in the api link as a query parameter which is returning "undefined" fixed by changing "client.user.id" to "client.user.self.id"
Can't figure out what im doing wrong!
In the previous fnbr v3.1.6 i used to do
and that token works in pretty much every api (including matchmaking, and it still works to this day)
in v4.0.0 i do
but this token throws in matchmaking service api ,the same api as before (both tokens look very similar)
i very much could be doing something wrong, help is greatly appreciated