Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.17f1
Issue ID
1108939
Regression
No
Addressables fails to build if Dependency is deleted but it is still used by the Build Cache
When attempting to Build our Addressable Asset Bundles Unity started throwing 'ArgumentException: Path is empty.' and 'FileNotFoundException' from HashingMethods.CalculateFile() at line 294. Upon investigating the cause of these Exceptions User found that they were coming from the Build Cache referencing Assets in their Dependencies that had been removed from the project.
To reproduce:
1. Download attached project “Addressables Dependancy Bug.zip" and open in Unity
2. Open “SampleScene” scene
3. Press Custom > Build Bundles menu item and wait until it completes
4. Delete the script "ReferenceScript" and remove its reference on the "MainPrefab" prefab
5. Press Custom > Build Bundles menu item again
Expected results: Addressables succeeds to build again
Actual results: Addressables fails to build and throws "ArgumentException: Path is empty" or "FileNotFoundException" from HashingMethods.CalculateFile() at line 294
Notes:
- This issue appears on both Windows and macOS
- This behavior causes thousands of LODGroups to become outdated while working on an actual level.
- Workaround: Delete Build Cache from Library folder
- Could not check on earlier Unity versions because the project becomes corrupted
Reproduced on Unity 2018.2.17f1, 2018.2.20f1, 2018.3.1f1 and 2019.1.0a12
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
User is no longer having the issue after using 0.5.3 Addressables Package