Search Issue Tracker
By Design
Votes
0
Found in
2021.3.27f1
2022.3.2f1
2023.1.0f1
2023.2.0a19
Issue ID
UUM-39925
Regression
No
Mac Player build can't be launched when it is built on a Windows machine
Reproduction steps:
1. Create a new project on a Windows machine
2. Open Build Settings (File > Build Settings) and set the “Target Platform” field to “macOS”
3. Build the project
4. Transfer the built project to any Mac machine and launch it
Expected result: The built Mac Player can be launched on any Mac machine
Actual result: When launching the Player a pop-up message appears saying “The application “{App Name}” can’t be opened.”
Reproducible with: 2021.3.27f1, 2022.3.2f1, 2023.1.0f1, 2023.2.0a19
Reproducible on: macOS 13.3 (Intel)
Note: A workaround for this would be changing the file permissions using a command in Terminal “chmod -R +x “{filename}.app”
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 RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
Resolution Note:
Since windows does not support unix permissions, whenever you transfer executable files from windows to mac or linux you also have to make them executable.