Search Issue Tracker
[OS X] Unix executable inside build's .app package derives its name from the project's product name instead of the build's name
How to reproduce:
1. Create a Unity project
2. In the "Edit" > "Build Settings..." window, build any Scene for the Mac OS X Standalone platform and make sure to give it a unique name
3. After the build is finished, open the folder where the build .app file is located in Finder
4. Right-click on the build .app file and press "Show Package Contents"
5. Navigate to "Contents" > "MacOS" and observe the name of the Unix executable file
Expected results: the Unix executable derives its name from the unique name of the build
Actual results: the Unix executable's name is identical to the product's name (found in the Player Settings)
Reproducible with: 2019.2.0a4, 2019.2.16f1, 2019.3.0f3, 2020.1.0a17
Not reproducible with: 2017.4.35f1, 2018.4.14f1, 2019.2.0a3
1. Until Unity 2019.2.0a3, the Unix executable in the Contents > MacOS folder is a document, but it is named after the build .app file.
2. Reproducible when building on Mac OS X Standalone on both macOS and Windows devices.
3. To observe the issue on a Windows device, build the project on Mac OS X Standalone, open the build directory through File Explorer, navigate to "Contents" > "MacOS" and note the file's name in the directory.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- [2020.3] Play Mode has visual artifacts when Graphics API is set to DirectX12 with Dynamic Resolution enabled
- White texture appears when setting “RenderTextureFormat.Depth” to “RenderTexture” on the Camera
- Cursor is visible when using “Cursor.lockState = CursorLockMode.Locked” and “Cursor.visible = false”
- Material.SetOverrideTag setting LightMode tag has no effect
- Decal is not rendered when in Camera component Culling Mask dropdown field Default is unselected