Search Issue Tracker
Active
Votes
1
Found in
2022.3.69f1
6000.0.63f1
6000.2.14f1
6000.3.0f1
6000.4.0a5
6000.5.0a2
Issue ID
UUM-129345
Regression
No
A wrong log file is attached when project is launched with a "-logFile" command line argument
How to reproduce:
1. Create a new project
2. In Unity Hub, press the three dots icon next to the project
3. Select "Add command line arguments" from the dropdown menu
4. Add a "-logFile" command line argument with a different location to the default one
5. Open the project using Unity Hub
6. In the menu bar select "Help" and "Report a Bug..."
7. Observe the Attachments
Actual result: A wrong log file from local AppData is attached
Expected result: The correct log file from the provided location is attached
Reproducible with: 2023.1.0a3, 2022.3.69f1, 6000.0.63f1, 6000.2.14f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note:
- no log file is attached in versions 2023.1.0a3 and 2022.3.69f1
- example of the command line argument on Windows: -logFile "C:\TestFolder\EditorTest.log”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment