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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment