Search Issue Tracker
Fixed
Fixed in 4.3.1, 6.0.6, 7.0.3, 8.0.0, 9.0.0-pre.1
Votes
25
Found in [Package]
2020.3.0
2021.3.0
2022.1.0
2022.2.0
2023.1.0
Issue ID
DANB-194
Regression
Yes
[2020.3] NullReferenceException is thrown when selecting a PSB file in the Project Browser
How to reproduce:
1. Open the user’s attached project
2. Select the “Fei-CLONE” PSB format file in the Project Browser
Expected result: Import Settings open in the Inspector
Actual result: “NullReferenceException: Max Size: SerializedProperty is null” is thrown in the Console log
Reproducible with: 2020.3.38f1
Not reproducible with: 2020.3.37f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b5, 2023.1.0a6
Reproduced on: macOS 12.3 (Intel)
Note:
When de-selecting the PSB file, “PSDImporterEditor.OnInspectorGUI must call ApplyRevertGUI to avoid unexpected behaviour.” is thrown
Comments (20)
- 
        dorusoftware Nov 08, 2022 13:36 
- 
        dorusoftware Nov 08, 2022 13:34 see my post here https://forum.unity.com/threads/psb-asset-inspector-window-is-breaking.1334079/#post-8571116 while you think you have updated to the latest package version which is 7.0.3 ,unity will still use 7.0.2 Yeah I know. anyway, i've posted a solution in that thread 
- 
        Leo-Yaik Oct 11, 2022 05:48 The issue has been fixed on the following package version. 
 If you are still encountering the issue after the upgrading to the relevant version, please help file a new issue so that we can look at it as it might not be the same cause. Alternatively, you can post at our forum page https://forum.unity.com/forums/2d.53/Unity 2022. 2 -> com.unity.2d.psdimporter@8.0.0 
 Unity 2022. 1 -> com.unity.2d.psdimporter@7.0.3
 Unity 2021. 3 -> com.unity.2d.psdimporter@6.0.6
 Unity 2020. 3 -> com.unity.2d.psdimporter@4.3.1
- 
        PenguinPotential Oct 08, 2022 01:16 JPERMAN8 I agree, I have not been able to work on my PSB files in my project in 2 weeks. This is a much bigger problem than Unity is saying it is. Please Unity move this up in your urgency list!!! 
- 
        jperman8 Oct 05, 2022 14:32 Can confirm - my collaboraters cannot even use the editor as cloning the project fresh causes the asset to not be resolved at all ( and thus the main player character cannot be controlled at all ! ) In my 5 years with Unity, this is by the far the most critical bug I've seen. For macs we have not found a version without this issue. For my windows machine, the only version that works for this is 2021.3.8f1 (I've tried 5+ different ones to no avail. Really want to know when this is truly fixed. 
- 
        JointWater Sep 23, 2022 02:46 Don't let fresh fish touch Importer or 2D Skinning Editor. They may destroy assets of many developers, such as sprite vertexes, meshes and bones. 
- 
        JointWater Sep 23, 2022 02:27 found in 2021.3.10f1 
- 
        PenguinPotential Sep 21, 2022 20:21 Looking forward to this fix. Just updated my project from 2020.2 to 2022.1 and cannot use PSD Importer anymore. Will be checking back daily 
- 
        FhyDay Sep 18, 2022 07:17 I also tried to use the beta version of Unity 2022.2.0b8 
 and with both 2D PSD Importer 8.0.0 and 8.0.0-pre3 - but still having the same issue
- 
        FhyDay Sep 18, 2022 06:38 2022.1.16f also faces this. 
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 9.0.0-pre.1):
Fixed in 2D PSDImporter 9.0.0-pre.1
Resolution Note (fix version 8.0.0):
Fixed in PSDImporter 8.0.0
Resolution Note (fix version 7.0.3):
Verified as fixed in PSDImporter 7.0.3
Resolution Note (fix version 6.0.6):
This is now fixed with PSDImporter 6.0.6
Resolution Note (fix version 4.3.1):
This is resolved in PSDImporter 4.3.1