Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
[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
- 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.
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset