Why are there cases where error responses are different?
SeungHeeMun-GGQ opened this issue · 3 comments
This is an issue that occurred while migrating from version 4 to 6.
I am curious as to why sometimes it responds with an error like 1 and sometimes it responds with an error like 2.
I want to manage error handling as a single response.
Is this the intended result? If not, I'm very curious about what the intention is.
I'm pretty sure the second error is a result from the LCU API as we don't return anything with { errorCode: number, errorMessage: string } anywhere in our code.
The first error happens when you send a request to the client before the REST server is initialized.
As stated above, the second one is a response from the client. It's possible that the endpoint you're trying to communicate with either takes a bit to initialize, or you're passing invalid parameters to it. The logs in {LeagueDir}/Logs/LeagueClient Logs may be able to help you debug issues with endpoint initialization.
The question has been resolved.
Thank you for answer.