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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment