Describe the bug
A bad API key will cause the API call to return a 401 response, and does not catch it.
This returns null to the ArmaMod.UpdateInfos loop and fails for each of it's tries, and has no check for all attempts failing.
ArmaModCollection.AddSteamMod adds the new mod before getting info on it, and doesn't do anything if info getting fails.
To Reproduce
Use a bad or expired API key. (through setup or by editing the config)
Add a new mod or mods through the mods page.
The new mod/mods will have no name or author and a size of 0.00B.
Expected behaviour
A mods info should be filled out.
If that is not possible it should raise an error, with the response type. And depending if it's a 401, prompt to update or remove the API key.
Actual behaviour
The fields of a mods info will be null; Name, Author, SteamLastUpdated, LocalLastUpdated, Size.
Describe the bug
A bad API key will cause the API call to return a 401 response, and does not catch it. This returns null to the ArmaMod.UpdateInfos loop and fails for each of it's tries, and has no check for all attempts failing. ArmaModCollection.AddSteamMod adds the new mod before getting info on it, and doesn't do anything if info getting fails.
To Reproduce
Expected behaviour
A mods info should be filled out. If that is not possible it should raise an error, with the response type. And depending if it's a 401, prompt to update or remove the API key.
Actual behaviour
The fields of a mods info will be null; Name, Author, SteamLastUpdated, LocalLastUpdated, Size.
Screenshots
![image](https://github.com/Foxlider/FASTER/assets/121286581/11359fd4-5c01-4938-9920-d33044f7a103)
OS Version:
Additional context