Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.

Postponed

Votes

0

Found in

5.1.1p2

Issue ID

958115

Regression

No

Unity does not notice scripting symbol changes in the ProjectSettings.asset file

Asset - Database

-

How to reproduce:
1. Open QA attached project
2. Enter play mode
-- A OnGUI window is displayed (expected)
3. Press 'Remove Developer Symbol From File'. This will remove 'DEVELOPER' symbol from ProjectSettings.asset
4. Enter play mode again
-- OnGUI window displayed. This is expected since the change was 'on disk'.
5. Reimport the 'TestSymbols.cs'
-- OnGUI window NOT displayed (expected, since it finally caught on that the symbol was removed)
6. In git (or any other VCS) undo local changes (ex: 'git checkout .')
7. Enter play mode
-- OnGUI window NOT displayed.

Expected behaviour: Unity should react to changes done to PlayerSettings.asset from VCS
Actual behaviour: Changes are ignored (just like a manual write) unless scripts are reimported.

Reproduced with: 5.6.4p4, 2017.1.2p4, 2017.2.1f1, 2017.3.0f2, 2018.1.0a7

  1. Resolution Note:

    This is a missing feature in the Asset Pipeline, it can only be addressed in the new Asset Pipeline backend when we switch.

Log in to vote on this issue

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.

Latest issues

See all new issues