Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a7
Issue ID
1133920
Regression
Yes
[macOS] Player.log is not opened after right-clicking the Console window and selecting 'Open Player Log'
How to reproduce:
1. Create a new Unity project
2. Build and Run the project to generate a Player.log file
3. Right-click the Console window and select 'Open Player Log'
Expected result: Player.log is opened
Actual result: nothing happens
Reproducible with: 2019.2.0a7, 2019.2.0a8
Not reproducible with: 2017.4.23f1, 2018.3.8f1, 2019.1.0b7, 2019.2.0a6
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note (fix version 2019.2):
Fixed in 2020.1. Also added the button to Windows and Linux editors.