wandermaus Posted May 31, 2023 Report Posted May 31, 2023 /workspaces/csgo-old-api/node_modules/simple-vdf/index.js:54 throw new SyntaxError("VDF.parse: invalid syntax on line " + (i+1)); ^ SyntaxError: VDF.parse: invalid syntax on line 6278 at Object.parse (/workspaces/csgo-old-api/node_modules/simple-vdf/index.js:54:23) at /workspaces/csgo-old-api/node_modules/steam-user/components/apps.js:237:21 at Array.forEach (<anonymous>) at SteamUser.<anonymous> (/workspaces/csgo-old-api/node_modules/steam-user/components/apps.js:233:24) at SteamUser._handleMessage (/workspaces/csgo-old-api/node_modules/steam-user/components/03-messages.js:639:35) at SteamUser._handleNetMessage (/workspaces/csgo-old-api/node_modules/steam-user/components/03-messages.js:562:8) at SteamUser._processMulti (/workspaces/csgo-old-api/node_modules/steam-user/components/03-messages.js:693:9) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) I have an application running where I use the "node-steam-user" package. Since yesterday, I get this error after login in to steam. Anything wrong on my end? Quote
Dr. McKay Posted May 31, 2023 Report Posted May 31, 2023 It looks like Steam might have changed how product info data is sent. Update to 4.28.5 and it should be fixed for you. Quote
wandermaus Posted June 4, 2023 Author Report Posted June 4, 2023 Thanks for your response. I updated, but get now this error: node:internal/process/promises:265 triggerUncaughtException(err, true /* fromPromise */); ^ OperationalError: HTTP error 404 at ClientRequest.<anonymous> (/app/node_modules/steam-user/components/cdn.js:585:13) ... 9 lines matching cause stack trace ... at TCP.onStreamRead (node:internal/stream_base_commons:190:23) { cause: Error: HTTP error 404 at ClientRequest.<anonymous> (/app/node_modules/steam-user/components/cdn.js:585:13) at Object.onceWrapper (node:events:640:26) at ClientRequest.emit (node:events:520:28) at HTTPParser.parserOnIncomingClient (node:_http_client:618:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17) at Socket.socketOnData (node:_http_client:482:22) at Socket.emit (node:events:520:28) at addChunk (node:internal/streams/readable:315:12) at readableAddChunk (node:internal/streams/readable:289:9) at Socket.Readable.push (node:internal/streams/readable:228:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23), isOperational: true } Quote
Dr. McKay Posted June 5, 2023 Report Posted June 5, 2023 This works fine for me: let manifestId = (await user.getProductInfo([730], [])).apps[730].appinfo.depots[731].manifests.public.gid; console.log(`Got manifest ${manifestId}`); console.log(await user.getManifest(730, 731, manifestId, 'public')); Please show your code. Quote
wandermaus Posted June 6, 2023 Author Report Posted June 6, 2023 I found the error. I guess in an earlier version, the GID got returned directly. Thanks for your help! Dr. McKay 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.