Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
1
Found in
2019.3
2019.3.1f1
2020.1
Issue ID
1221132
Regression
No
[macOS Standalone] Bundle Identifier in Player Settings does not match Xcode project bundle identifier on macOS Standalone
How to reproduce:
1. Create a new project for standalone OSX platform
2. Set a custom bundle identifier for example "com.com.test" in Player settings
3. In the Build Settings enable "Create Xcode Project" and press Build
4. Open generated Xcode project and notice the bundle identifier is "com.unity3d.New Unity Project"
Expected: generated Xcode project copies the Bundle Identifier from the Player Settings
Actual: Xcode sets new Bundle Identifier "com.unity3d.New Unity Project"
Reproducible with: 2019.3.2f1, 2020.1
Notes:
- This feature was introduced in 2019.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
Add comment