-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when starting backend #141
Comments
No worries :) |
Never mind, I can wait for you. If you need help due to regional problems during the repair process, I can help you as much as possible. If you can, please inform me after the repair is completed |
Would you be able to download the newest version and try it again, please? |
I'm glad I'll tell you a good news! I found a new lockfile file that follows the launch of the game client, and copied the contents to the abandoned lockfile. Fortunately, the back end is running normally, which may be that you need to modify the path to obtain the lockfile file. I can see in the web link that the program is working very hard to obtain the information of the client. However, there is a new problem. As in #113 and #114, "waiting for league client to connect" appears in the back-end content. I tried the solving instructions in #113 and #114, but they didn't seem to work. I used "NPM start - debug - experimentalconnector - leaguepath" C: \ riot \ riot games \ League of Legends "to prompt" not connected to LCU, but distributed to get data ", and" NPM start - debug - experimentalconnector "to prompt" ready connected, Not checking ". Is there another solution? I will continue to try to change the path in the first instruction and try to repair it. |
As far as I can tell, the backend successfully connected with the alternative lockfile. Do you get events and the UI popping up when entering a champ select? We will look into adding an option to connect with this alternative method once we find time – for now manually changing the lockfile contents might be a workaround. |
I tried to use the tool in #141 branch to link with the alliance client, and it reported a new error, unable to verify the first certificate |
Sorry, I didn't mention that this should be without the experimental connector (that one still uses the old method). |
ok to test out if the lcu API works for you as it does for us, could you please start the backend to get the password and port. after you started that please start a champ select then. Then go to https://127.0.0.1:PORT/lol-champ-select/v1/session and replace PORT with the port from the console. If you get asked for login details type in 'riot' as username and the password you got from the console. |
Do you need this screenshot? It looks as if it's working properly |
Could you please provide the context as text instead of a screenshot? |
Sorry, the text is as follows:
|
Ok, this looks completely fine, all the info is present as expected. Could you try starting the backend with this command to test if the frontend works as expected? |
And if that's no use either, could you please tell us which node version you are using? just use |
I tried NPM Ci and NPM start again, but it still doesn't work properly. My node version is V16.7.0, maybe my node version is wrong? |
No, this is the node version we test/develop on. |
The back-end operation looks very good, but it is very strange that the status of variables not queried is always displayed on the page :( In the previous test instructions, I noticed that the value of the variable champselectactive is true. However, during the formal run, the value of the variable becomes false. Is this the problem? |
Just to make sure we're not chasing any ghosts: In theory, champSelectActive should flip to true as soon as the session endpoint returns any data (which we have confirmed it does), which is why we are confused :( |
I can't see anything. I tried it again according to the process you suggested, and it didn't work. If it is convenient for you to provide your email to me, I can record a video of the starting process to you. As for reading the returned data of the session endpoint, will it be caused by the same reading error as the previous lockfile? For example, the client does return some values, but the back-end read path deviates. |
Good news! I tried to download and install the riot client to run the league of legends. Based on the riot client, the UI successfully ran on the web! Obviously, the front-end and back-end are normal, and the problem appears on Tencent client. However, I can't find out the difference between the two clients. Maybe you can help adapt the back end to Tencent client when you are free. After all, the riot client does not support servers in China. I have to run the UI with more than 300 Ping, which is very difficult. So that I can't hold a very formal competition among my friends. Thank you very much for your technical support |
We gonna put it on the list of stuff to improve and fix, but pls be aware that this may take a bit for us to figure out. |
I'm very sorry that it was #138 closed due to my wrong operation.
After I use the instructions you #138 provided, the content displayed on the backend is as shown in the figure
The text was updated successfully, but these errors were encountered: