Closed humor4fun closed 1 month ago
Hey there! Thank you for contacting our development team at GitHub.
We believe that your issue does not meet our contributing guidelines referenced during issue creation.
Before you open an issue please review the contributing guidelines for this repository. (...) I understand that if my issue is not meeting contributing guidelines specified above, especially if it's a question or technical issue that is not related to ASF development in any way, then it will be closed and left unanswered.
Reason for closing: technical difficulties using the program are not related to ASF development. Use appropriate support channel instead.
Please check out our wiki if you need further help.
Have a nice day! ~Archi
Looks like you are using a third-party plugin causing the issues. Contact your third-party vendor instead.
It would be useful if the log indicated what plugin was being loaded at the time of the error.
If ASF knew which plugin was causing that then it'd let you know.
@JustArchi since we're not loading plugins in parallel, I believe we could add a "debug" log before the call to Assembly.LoadFrom(assemblyPath)
in which we log the path to the binary. Imagine it such as Attempting to load plugin from file: {0}
Edit: related code
@Abrynos next time analyze better.
But wouldn't this exceptions still happen AFTER assembly load? I'm sorry, I don't understand how it works, just asking.
As you can see from existing code, no, assembly load works fine, using it fails, and we can't call every single function, property, interface, class and explore every single line of assembly to determine whether or not it's valid.
If ASF knew which plugin was causing that then it'd let you know.
If you have actual code suggestion how to improve this part, send a PR.
I've added https://github.com/JustArchiNET/ArchiSteamFarm/commit/a27973800c2bc2e4edc956d291cc0e76b211d0c3 to give slightly more info, as that's the only thing ASF can possibly do in this case that comes to my mind.
Checklist
ASF version
Latest stable release
ASF variant
win-x64
Bug description
One day after running normally for many weeks i went to start ASF up and it just refused to load throwing me this error message. So I went to get the latest version and it shows the same error message when i try to run the exe.
Expected behavior
ASF runs
Actual behavior
ASF throws this error, stalls for about 10 seconds, then closes
Steps to reproduce
No response
Possible reason/solution
No response
Can you help us with this bug report?
Somehow, I can test and offer feedback, but can't code
Full log.txt recorded during reproducing the problem
Global ASF.json config file
No response
BotName.json config of all affected bot instances
Additional info
No response