Skip to content
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

steamcmd +app_info_update does not grab app info #11562

Closed
jack-avery opened this issue Dec 12, 2024 · 1 comment
Closed

steamcmd +app_info_update does not grab app info #11562

jack-avery opened this issue Dec 12, 2024 · 1 comment

Comments

@jack-avery
Copy link

jack-avery commented Dec 12, 2024

Your system information

(These are the system settings for https://hub.docker.com/r/cm2network/steamcmd)

  • Steam client version (build number or date): Steam Console Client (c) Valve Corporation - version 1733269577
  • Distribution (e.g. Ubuntu): Debian GNU/Linux 12
  • Opted into Steam client beta?: [Yes/No] No
  • Have you checked for system updates?: [Yes/No] Yes
  • Steam Logs: N/A, see below
  • GPU: N/A

Please describe your issue in as much detail as possible:

I use a disgustingly long one-liner here to check for Team Fortress 2 Linux Dedicated Server (232250) updates automatically. It has worked wonderfully so far, but I noticed today after the holiday patch that the +app_info_update 232250 part doesn't seem to work:

steam@09b71f1cd798:~/steamcmd$ ./steamcmd.sh +login anonymous +app_info_update 232250 +app_info_print 232250 +quit
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1733269577
-- type 'quit' to exit --
Loading Steam API...IPC function call IClientUtils::GetSteamRealm took too long: 52 msec
OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
No app info for AppID 232250 found, requesting...

... running app_info_print again within the same container after a bit will print the correct information, however, using a duplicate +app_info_print in the command-line parameters as an attempted workaround will instead will just print an empty data object:

"232250"
{
}

My updater log states it hasn't successfully checked for an update since November 26th:

[11/26/24 21:00:01] (3515963) Checking...
[11/26/24 21:00:19] Current: 16411573; Latest: 16411573
[11/26/24 21:00:19] Current is latest, nothing to do

[11/26/24 21:10:02] (3516248) Checking...
[11/26/24 21:10:18] Current: 16411573; Latest:
[11/26/24 21:10:18] Failed to fetch latest, doing nothing

Edit: probably possible to work around using a sleep to force the container to wait for the info... but I would rather not do that, personally, and I think this is undesirable behavior, so I am reporting it.

Steps for reproducing this issue:

  1. Run steamcmd.sh using the following command-line parameters: ./steamcmd.sh +login anonymous +app_info_update 232250 +app_info_print 232250 +quit
@kisak-valve
Copy link
Member

Hello @jack-avery, this issue is already being tracked at #9683. Closing as a duplicate.

@kisak-valve kisak-valve closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants