Search Unity

[2018.3.8f1][0.6.7][Case 1138947] AAS completly broken

Discussion in 'Addressables' started by MNNoxMortem, Mar 20, 2019.

  1. MNNoxMortem

    MNNoxMortem

    Joined:
    Sep 11, 2016
    Posts:
    723
    We somehow managed to completly break the AAS. It does not read the groups correctly and one group is missing

    The none group is the Prefabs.asset group

    Which is completly broken and does not show an inspector

    P4 merge does not show any difference to the file on the PC where it is broken
    upload_2019-3-20_17-17-16.png
    to the PC where it works
    upload_2019-3-20_17-17-33.png
    These are the errors the AAS reports
    Code (CSharp):
    1. [Exception] NullReferenceException: Object reference not set to an instance of an object
    2. AddressableAssetSettings.IsNotUniqueGroupName()    Library/PackageCache/com.unity.addressables@0.6.7-preview/Editor/Settings/AddressableAssetSettings.cs:1214
    3.  
    4. AddressableAssetSettings.FindUniqueGroupName()    Library/PackageCache/com.unity.addressables@0.6.7-preview/Editor/Settings/AddressableAssetSettings.cs:1198
    5.  
    6. AddressableAssetSettings.CreateGroup()    Library/PackageCache/com.unity.addressables@0.6.7-preview/Editor/Settings/AddressableAssetSettings.cs:1156
    7.  
    8. AddressableAssetEntryTreeView.CreateNewGroup()    Library/PackageCache/com.unity.addressables@0.6.7-preview/Editor/GUI/AddressableAssetsSettingsGroupTreeView.cs:824
    9.  
    10. GenericMenu.CatchMenu()    C:/buildslave/unity/build/Editor/Mono/GUI/GenericMenu.cs:119
    11.  
    As well as:
    https://pastebin.com/R916RThv
    https://pastebin.com/ayZbhLid
    https://pastebin.com/HNKtzSQP
     
    Last edited: Mar 20, 2019
  2. MNNoxMortem

    MNNoxMortem

    Joined:
    Sep 11, 2016
    Posts:
    723
    Okay that one was scary. Not even deleting /Library and /Obj helped to restore this. Neither copying the whole AAS folder into the project from a station where it worked helped - likely because the .meta and ids did not match.

    Only recreating all settings helped.
     
  3. MNNoxMortem

    MNNoxMortem

    Joined:
    Sep 11, 2016
    Posts:
    723
    The deserialization fails and that seems to be the problem in this project.
    Code (CSharp):
    1. [Exception] ArgumentException: Object at index 0 is null
    2. UnityEditor.SerializedObject..ctor()    C:/buildslave/unity/build/Editor/Mono/SerializedObject.bindings.cs:23
    3.  
    4. AddressableAssetGroupSchema.OnGUI()    Library/PackageCache/com.unity.addressables@0.6.7-preview/Editor/Settings/AddressableAssetGroupSchema.cs:50
    5. 48:   {
    6. 49:       var type = GetType();
    7. -->50:       var so = new SerializedObject(this);
    8. 51:       var p = so.GetIterator();
    9. 52:       p.Next(true);
    10.  
    11. AddressableAssetGroupInspector.OnInspectorGUI()    Library/PackageCache/com.unity.addressables@0.6.7-preview/Editor/GUI/AddressableAssetGroupInspector.cs:103
    12. 101:   try
    13. 102:   {
    14. -->103:       schema.OnGUI();
    15. 104:   }
    16. 105:   catch (Exception se)
    17.  
    18. GUIUtility.ProcessEvent()
    19.  
    And it creates a whole bunch of new assets
    upload_2019-3-20_20-23-16.png

    And this gif shows how the Default Local Group is broken and cannot be serialized/deserialized correctly
     
    Last edited: Mar 21, 2019
    RecursiveFrog likes this.
  4. unity_bill

    unity_bill

    Joined:
    Apr 11, 2017
    Posts:
    1,053
    Hey @MNNoxMortem - really sorry to see this happening. Looks like a weird upgrade issue. Were you going form 0.5.3 up to 0.6.7? or from something older?

    -Bill
     
  5. MNNoxMortem

    MNNoxMortem

    Joined:
    Sep 11, 2016
    Posts:
    723
    @unity_bill Can happen :) The big problem just was that this was infectious. We recreated the settings, committed the changes and when the next person pulled it - bam :)

    Also I should note that this was not during the update progress but later. So we were already using 0.6.7 successfully for some time, but as it was still timely close enough to the usage of 0.5.3 this might be related to switching branches between 0.5.3 and 0.6.7 and from my experience with unity stuff likey this (usually more when those branches do not share the platform or unity editor version) sometimes can still lead to some problems with de/serialization. However, this is just an uneducated guess, but I try to provide all information which comes to my mind.

    Yes we were upgrading form 0.5.3 to 0.6.7 and at the moment it works. Even on the station where it broke initially he does not see any group labels (just empty) but everything else seems to work again after creating everything new.