Search Issue Tracker

Won't Fix

Votes

0

Found in

2021.3.45f1

2022.3.52f1

6000.0.27f1

6000.1.0a4

Issue ID

UUM-87133

Regression

No

Product name and Product version fields are not set properly when building a project as a Windows application

--

-

How to reproduce:
1. Open the attached “IN-88236“ project
2. Build the project
3. Open the folder containing the built project in File Explorer
4. Right-click on the project executable
5. Open the file details tab (Properties > Details)
6. Observe the values in the "Product name" and "Product version" fields

Expected result: The "Product name" and "Product version" fields contain the text "Test Name" and "1.23.4" respectively
Actual result: The "Product name" field is empty, and the "Product version" field contains the Unity Editor version used to build the project

Reproducible with: 2021.3.45f1, 2022.3.52f1, 6000.0.27f1, 6000.1.0a4

Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested

Note: The issue occurs when the application is built both with and without custom Windows Build Profiles

  1. Resolution Note:

    The Unity Runtime player executable is pre-compiled and signed with Unity's signature during our release process. Any changes made to the executable after would invalidate that signature.

    Modifying the executable's metadata (like product name and version info) would need it to be re-signed. This is something that users would need to set up as a custom build step for their own projects right now.

    While it might be interesting to evaluate if Unity could offer this as a feature in the Editor's project build process in the future, it's unlikely we'll be able to implement this soon.

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.