Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2018.3.0a5
2018.3.6f1
Issue ID
1131432
Regression
Yes
[Scripting] Define Constraints are available for Native Plugins even though they only work for Managed Plugins
Define Constraints should only be visible for Managed Plugins, not Native ones, but they are still visible/available in the Inspector. This should be removed for Native plugins
To reproduce:
1. Download attached project "test_unity_project.zip" and open in Unity
2. In Project view select Plugins > Android > PLUGIN_NAME (check Edits below) which is Native Plugin
3. Observe that in Inspector window Define Constraints have added KSDK_RELEASE constraint but this shouldn't be allowed
Notes:
- Would probably be good to also mention in docs: https://docs.unity3d.com/ScriptReference/PluginImporter.DefineConstraints.html that Define Constraints feature is only for Managed Plugins
Reproduced on Unity 2018.3.0a5, 2018.3.7f1, 2019.1.0b5 and 2019.2.0a6
Not reproduced on Unity 2018.2.20f1 and 2018.3.0a4
Regression on Unity 2018.3.0a5
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
- 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
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
Lars-Blaabjerg
Oct 11, 2021 10:30
I think a better fix would be to support them for native plugins. I need that :-/