jloh02 / valorant-chat-client

Access VALORANT chat without opening the game
https://jloh02.github.io/projects/valorant-chat-client/
MIT License
15 stars 1 forks source link

Says "Waiting for response" even though Riot Client is opened and signed in #2

Closed riahc3 closed 2 years ago

riahc3 commented 2 years ago

I have Riot Client opened and I am signed in but it says "Waiting for response" all the time

jloh02 commented 2 years ago

I've noticed this bug once in awhile but current unable to pinpoint exactly why. Restarting Riot Client and/or the application sometimes works. Is it possible to provide me your logs located under %APPDATA%\valorant-chat-client\logs?

riahc3 commented 2 years ago

[2022-06-08 20:54:46.669] [info] [Logger] Deleting old logs: vcc-20220606-202707.log [2022-06-08 20:54:46.673] [info] [Logger] Deleting old logs: vcc-20220606-202910.log [2022-06-08 20:54:46.674] [info] [Logger] Deleting old logs: vcc-20220606-222714.log [2022-06-08 20:54:46.676] [info] [Background] Lock Retrieved and log initialized [2022-06-08 20:54:49.624] [info] [Preferences] Path to Preferences: C:\Users\riahc\AppData\Roaming\valorant-chat-client/preferences.json [2022-06-08 20:54:49.631] [info] [Preferences] Found preferences: {"minimizeToTray":true,"notifications":true,"winWidth":1200,"winHeight":800,"winX":634,"winY":196} [2022-06-08 20:54:49.805] [info] [Background] Main window created [2022-06-08 20:54:49.916] [info] [Background] Tray created [2022-06-08 20:54:49.916] [info] [Background] VALORANT API initialized [2022-06-08 20:54:50.289] [info] [WINDOWS] Uninstall Path: "C:\Riot Games\Riot Client\RiotClientServices.exe" --uninstall-product=valorant --uninstall-patchline=live [2022-06-08 20:54:50.567] [info] Checking for update [2022-06-08 20:54:50.572] [error] [VALORANT] LocalAppData Error: {"errno":-4058,"syscall":"open","code":"ENOENT","path":"C:\Users\riahc\AppData\Local\Riot Games\Riot Client\Config\lockfile"} [2022-06-08 20:54:50.576] [info] [VALORANT] Lockfile data: undefined [2022-06-08 20:54:51.227] [error] Error: Error: No published versions on GitHub at Object.newError (C:\Program Files\VALORANT Chat Client\resources\app.asar\node_modules\builder-util-runtime\out\index.js:47:19) at GitHubProvider.getLatestVersion (C:\Program Files\VALORANT Chat Client\resources\app.asar\node_modules\electron-updater\out\providers\GitHubProvider.js:88:42) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async NsisUpdater.getUpdateInfoAndProvider (C:\Program Files\VALORANT Chat Client\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:305:19) at async NsisUpdater.doCheckForUpdates (C:\Program Files\VALORANT Chat Client\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:319:24) [2022-06-08 20:54:55.581] [info] [VALORANT] Lockfile data: Riot Client:5752:1137:3t_sRqxqfvwEQDVxxTGrQg:https [2022-06-08 20:54:55.582] [info] [VALORANT] Region: eu [2022-06-08 20:54:55.583] [info] [VALORANT] Shard: eu [2022-06-08 20:54:58.705] [info] [VALORANT] Entitlement: {"errorCode":"RPC_ERROR","httpStatus":400,"implementationDetails":{},"message":"Entitlements token is not ready yet"} [2022-06-08 20:56:33.345] [info] [WINDOWS] Uninstall Path: "C:\Riot Games\Riot Client\RiotClientServices.exe" --uninstall-product=valorant --uninstall-patchline=live [2022-06-09 01:06:52.886] [info] [WINDOWS] Uninstall Path: "C:\Riot Games\Riot Client\RiotClientServices.exe" --uninstall-product=valorant --uninstall-patchline=live [2022-06-09 19:48:46.025] [info] [WINDOWS] Uninstall Path: "C:\Riot Games\Riot Client\RiotClientServices.exe" --uninstall-product=valorant --uninstall-patchline=live [2022-06-09 19:50:09.558] [info] [WINDOWS] Uninstall Path: "C:\Riot Games\Riot Client\RiotClientServices.exe" --uninstall-product=valorant --uninstall-patchline=live [2022-06-09 21:46:49.728] [info] [WINDOWS] Uninstall Path: "C:\Riot Games\Riot Client\RiotClientServices.exe" --uninstall-product=valorant --uninstall-patchline=live

jloh02 commented 2 years ago

I was unable to recreate this error but based on your logs, I have patched the code and it should be reflected in 1.0.3. Do let me know if any errors still occur.