Addressables AssetReference "None" value is not saved in Editor when used in Prefab

Open

#33 opened on Apr 29, 2020 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: csharp, unity
Domain: game-dev

Research direction

Start with the attached project, open SampleScene, and reproduce the issue on the ObjectWithReference instance by changing Asset Reference to None, saving, reloading, and checking the Inspector. Trace how the prefab instance value is saved and restored; done means None remains None after the scene is saved and reloaded.

Written by the indexing model from the issue text.

Description

There is a public field of Addressables.AssetReference type in MonoBehaviour component.
This component is attached to a GameObject that is converted into prefab. Then prefab instance is added to the Scene. Changing field value to anything except "None" (empty) works fine. But after the value has been changed to anything it can not be changed back to "None" (empty value).
Changing value inside of the Prefab to anything except "None" partially solves the problem, but that's not a solution because it forces the prefab to keep reference to some object.
 
Steps to reproduce:
2.1. Open project attached.
2.2. Open the SampleScene and select ObjectWithReference instance on the Scene.
2.3. In Inspector change value of field "Asset Reference" to "None".
2.4. Save the Scene.
2.5. Reload the Scene.
2.6. Select ObjectWithReference instance on the Scene.
2.7. Result: the value is not "None" but the reference to the object that was set before.
Expected result: the value is set to "None".

Dominant language: C#
Stars: 1.5k
Forks: 303
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.