Unity windows standalone build crashes on opening output_log.txt if built on a different machine
We have a project where building the same windows standalone exe crashes if it comes from someone else's computer, but it works when built on mine.
I checked what happens with process monitor, and apparently the CreateFile operation by the exe on the path C:\Users\MYUSER\AppData\LocalLow\DefaultCompany\PROJECT\output_log.txt results in a NAME INVALID result. If open the exe built on my machine, the same operation with the same path results in a SUCCESS operation.
Failed attempt: opening windows error reporting
Successful attempt
Any idea what could cause this?
Your answer
Follow this Question
Related Questions
How can I show a prompt for the user when my standalone application crashes? 0 Answers
Avoid Unity3D internal log source from Player.log 3 Answers
Unity Dashboard- Crashes and Exceptions logs shows only Android and not IOS 0 Answers
Using Unity FBX exporter in standalone build 0 Answers
undefined symbol error related to WebRTC while building in Xcode 0 Answers