Search Issue Tracker
Fixed in 6000.0.23f1
Fixed in 6000.0.X, 7000.0.0a17, future release
Votes
0
Found in
6000.0.0b16
6000.1.0a7
Issue ID
UUM-70188
Regression
No
[Player Settings] [Common] [Configuration] - Scripting Backend - Non active build profile should check its player settings scripting backend and not global one to display warning
Steps to reproduce:
1. Open File > Build Profiles
2. Create two build profiles and player settings to them (press Customize Player Settings)
3. Change the scripting backend to IL2CPP (make sure it's not installed) and then make the build profile active. Make sure the other one is set to Mono
Actual results: All build profiles will show the script backend warning in the UI, even though one of them is set to Mono
Expected results: Each build profile should show the warning depending on it's player settings value
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (fix version future release):
Verified the scripting backend warnings for a build profile are correct and independent from the value of the project setting value.
Resolution Note (fix version 6000.0):
Fixed the bug where build profiles that show a warning in their settings UI based on the scripting backend were using a method that retrieved the project settings player settings value, instead of the build profile player setting value.