Search Issue Tracker
By Design
Votes
0
Found in
4.5.0b5
Issue ID
601194
Regression
Yes
Master configuration will show Development Build if project was exported with Development Build checked
Master configuration will show Development Build if project was exported with Development Build checked
Steps to reproduce:
1. Open any project or attached one
2. Check Development Build and build to folder
3. Open exported Visual Studio solution, select Master configuration
4. Deploy it to device. Development Build watermark will be shown, but Profiler will be disabled.
Why is this by design?
This is intended behaviour.
When Development Build is selected, ENABLE_PROFILER is defined and can be used in user scripts, resulting in different binary (with some profiler related code, not intended for final release).
Documentation also mentions this: development watermark is shown if either scripts were compiled with 'Development Build' or non-master configuration is used or both.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Masks affect Sprite Renderers outside their range when a Light2D is present with specific Target Sorting Layers selected
- URP Lens Flare is rendered in the wrong position when Render Graph Compatibility Mode is enabled and Render Scaling is not 0
- Editor crashes on DrvPresentBuffers when loading RenderDoc while using OpenGLES 3.0 or OpenGLES 2.0 Graphics API
- [Test Runner] Incorrect name under Window > Panel after project restart
- [iOS] Crash when using fallback fonts created at runtime
Add comment