Closed Ostabo closed 7 months ago
It can't find your LocalApplicationData folder. Is there anything unusual about your setup that would prevent an app from finding standard Windows configuration folders?
I get this as well, nothing unusual about my setup. Can reproduce by fresh installing it on a bone stock Windows 11 VM.
If you Run "%LOCALAPPDATA%", does it open a folder, and if so, is there a TarkovMonitor folder within that folder?
Appdata/Local -> TarkovMonitor -> TarkovMonitor_Path_gu5...
The TarkovMonitor folder is present and contains 2 subfolders - 1 containing another two subfolders for the versions I had installed, and one only containing the current 1.2.3 version i switched back to
Appdata/Local -> TarkovMonitor -> TarkovMonitor_Path_gu5...
The TarkovMonitor folder is present and contains 2 subfolders - 1 containing another two subfolders for the versions I had installed, and one only containing the current 1.2.3 version i switched back to
Same here
For some users, Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData)
is resolving to null. It should give the path for the user's %LocalAppData% folder. That path is used to create/access the local sqlite database that the app uses for storing raid and flea sales data for displaying statistics. Because it can't resolve that path, the database can't be created, and anything that would access the database causes the app to crash. These crash triggers are:
Can someone experiencing this issue please try this build: https://github.com/the-hideout/TarkovMonitor/actions/runs/7865137539/artifacts/1236961902
I cloned the repo (not the build linked above) to try and step through it to see what might be happening. Malwarebytes wants to quarantine the DLL, but after allowing that, it seems to work fine when I build it myself..
Can someone experiencing this issue please try this build: https://github.com/the-hideout/TarkovMonitor/actions/runs/7865137539/artifacts/1236961902
This build crashes for me
Does it happen to work if you run as administrator?
Does it happen to work if you run as administrator?
Negative
I know where the error is occurring, I just can't figure out why some PCs fail to resolve these appdata folders properly.
As I mentioned above, if I build the solution myself with no changes, I can execute the build without errors. You have an additional packaging step that I do not know, but perhaps something in that is causing the issue? At least I assume you do, my build has a bunch more files.
Oh yeah I think I might know what's going on.
This should be resolved in the latest release.
German equivalent of unhandled exception, after clicking on the new stats navigation
I assume the path is not set
Details: