Search Issue Tracker

By Design



Found in






Issue ID




"Development Build" watermark is shown in non-development UWP release builds



Reproduction steps:
1. Open the “Test UWP Dev Stripped“ project
2. Open the “SampleScene” scene
3. In Build Settings ensure the selected platform is “Universal Windows Platform”, configuration is “Release”, and Development Build is unchecked
4. Build and in the built folder open the “Test UWP Dev.sln” solution
5. In Visual Studio ensure the configuration is “Release”, the platform is “x64”, and the startup project is “Test UWP Dev (Universal Windows)”
6. Start on the local machine and observe the bottom right of the Player

Expected result: no “Development Build“ watermark
Actual result: “Development Build“ watermark

Reproduced in: 2020.3.46f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a7

Reproduced using: Windows 10 (by the reporter), Windows 11
Could not reproduce using: macOS 13.2.1 (Intel) (UWP not available)

Note: also reproduced in AppX

  1. Resolution Note:

    This is by design. On UWP, you can switch between development and non-development builds via build configuration option in Visual Studio. Debug & Release configurations represent development build, and Master configuration represents a non-development build. For UWP, the only thing that the "Development build" checkbox controls is "DEVELOPMENT_BUILD" define for your C# scripts and packages.

    This is also applicable to other platforms that allow you to change build configuration separately from development build checkbox. For instance, if you check "Create Visual Studio Solution" when building for Windows Standalone player, you will be able to observe the same behaviour in Visual Studio as on UWP.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.