System.ArgumentNullException: Value cannot be null #3029
Comments
MsFloofie
added
🐛 Bug
|
I can report that the issue is happening on the arm64 macOS build as well. Trying the latest pre-release version results in the same issue. EDIT: Spun up an x86-64 Debian 12 VM, same issue. |
|
same in win x64 |
|
Encountering same issue on Linux armx64 and winx64 just after confirming steam guard or entering steam guard code. Both worked perfectly earlier today, now both giving the same error. Even on brand new install with correct dependencies. Full windows log attached. |
This comment was marked as spam.
This comment was marked as spam.
|
Same on Docker version. |
|
This started after the weekly maintenance an hour ago. |
|
Same here, Windows 11 pro x64. |
|
Same issue, tried to re-run after Steam maintenance, Windows 11 Pro x64 / ArchiSteamFarm V5.4.10.3 |
|
Getting issue on arm64 (pi 4, docker) so safe to assume something in the api has changed? It doesn't seem to be stuck to any specific architecture/OS. |
This comment was marked as spam.
This comment was marked as spam.
|
Same error on docker ARM |
This comment was marked as spam.
This comment was marked as spam.
|
I'm experiencing a similar situation on my Debian 12 server. |
|
2023-10-18 07:16:45|ArchiSteamFarm-36972|INFO|//one of 4 bots. different on every restart//|OnLoggedOn() Successfully logged on as //one of 4 bots. different on every restart// win 10 (1909), ASF: 5.4.10.3 |
|
2023-10-18 09:06:10|ArchiSteamFarm-1280|ERROR|ASF|Exit() 正在以非 0 错误代码退出！ BY windows professor version x64 |
On Raspi4 aarch64 |
This comment was marked as spam.
This comment was marked as spam.
1 similar comment
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as duplicate.
This comment was marked as duplicate.
|
Same problems with openwrt system Docker (Armv8(Arm64) Linux) [10:14:53] FATAL ASF > OnUnhandledException() System.ArgumentNullException: Value cannot be null. (Parameter 'webAPIUserNonce') |
|
Same Issus in Debian 11 X86 system |
This comment was marked as spam.
This comment was marked as spam.
|
Tested ASF 5.4.0.3 to ASF 5.4.10.3, all have the same issue |
|
Confirm issue |
|
Same on my mac(arm64, m1 pro): Maybe some API change but u still use it? |
|
Also happening on Linux x64 (Ubuntu 22.04.3 LTS) |
|
same in osx-x64 |
|
same on linux amd64 |
|
Just skip the null check here, and it works |
|
Same. Centos docker: |
|
Same!! mac(arm64) V5.4.10.3 and [V5.4.11.2] |
|
+1 Lmfao I thought I was going crazy....... I was googling keywords for the past hour or so and reading so many articles. Tried so many different things to fix it, did some trial and error using multiple new vps iterations... new accounts, new configs, new releases... and I'm an idiot because only THEN did I decide I'd go look in the issues section. doy |
|
This seems to be a general issue regardless the SO nor the version of the program. Let's try to keep this issue as clean as possible by posting only useful information. Devs might be already working on a solution, don't panic. If you need to follow this issue, there's a Subscribe button on the right panel (If you're on web), or in the three dots menu (on Mobile) |
This comment was marked as spam.
This comment was marked as spam.
|
|
|
I think by now we have enough information to prove something happened after yesterday's maintenance window, and it's not a problem with the operating system or architecture. And we do have a band-aid fix. Since this seems to be related to the Web API component of the handler. Beyond assuming the main developer(s) are on the case, how could we validate against the Steam API? stuff like SteamDB and ProtonDB must have failed in similar ways now, or in the past, surely. |
JustArchi
added
✔️ Confirmed
|
After today's maintenance, Steam stopped sending web token nonce - something that is required for establishing web session and making ASF work. Fortunately we can ask for that token regardless whether or not it arrives in the callback, which is what my fix above actually does, fixing the underlying issue. Fixed in V5.4.11.3, which will be released and promoted to stable shortly. Since this crash happens after bots are being started, and update procedure normally happens before bots initialization, launching old version will suffice the moment new release is available. Thanks for report and details! 👍 |
Bot does not send exchanges when receiving a new web token nonce. Error 401 (unauthorized) pops up, although some actions work with this authorization. |
This comment was marked as abuse.
This comment was marked as abuse.
Works fine for me, nothing like that is required. I don't know what you're using, but if official release and not some hotfixed by other people than me then open new issue with log and all required details, this issue is done with. |
|
It seems to be fixed in 5.4.11.4: Thank you ASF team and contributors for a quick support. |
|
Thanks for the quick release of v5.4.11.4 |
JustArchi
added
🔴 High priority
This comment was marked as off-topic.
This comment was marked as off-topic.
and others
Checklist
ASF version
Latest stable release
ASF variant
linux-arm64
Bug description
After the Steam maintenance on October 17th, 2023, ArchiSteamFarm is unable to start back up, reporting a FATAL log with
System.ArgumentNullException: Value cannot be null. (Parameter 'webAPIUserNonce')Full FATAL message below
Expected behavior
ASF was expected to connect back to steam servers after the maintenance
Actual behavior
ASF automatically shuts down with a fatal error message.
Steps to reproduce
Possible reason/solution
No response
Can you help us with this bug report?
No, I don't have time, skills or willings for any of that
Full log.txt recorded during reproducing the problem
Global ASF.json config file
No response
BotName.json config of all affected bot instances
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: