Search Issue Tracker
By Design
Under Consideration for 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.9f1
2023.1.13f1
2023.2.0b9
2023.3.0a5
Issue ID
UUM-48934
Regression
No
ENABLE_MONO and ENABLE_IL2CPP directives are incorrectly defined when entering Play mode
Reproduction steps:
1. Open project “Test_IL2CPP_Conditional_Compilation.zip”
2. Open “SampleScene”
3. Make sure the IL2CPP scripting backend is set in the Project Settings
4. Enter Play mode
Expected result: The editor exits play mode and prints a "{*}IL2CPP scripting backend is enabled{*}." log message in the Console
Actual result: The editor exits play mode and prints a "{*}Mono scripting backend is enabled{*}." log message in the Console
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a5
Reproducible on: macOS Ventura 13.2.1 (Intel)
Not reproducible on: no other environment tested
Notes:
- Not reproducible in Standalone Player
- ENABLE_MONO directive is always defined whereas ENABLE_IL2CPP is never defined, regardless of whether the scripting backend is set to Mono or IL2CPP
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 when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
`ENABLE_IL2CPP` are only set if the current running scripting backend are IL2CPP. Playmode always runs Mono.
`ENABLE_IL2CPP` will only be for player builds with the il2cpp scripting backend selected.