Search Issue Tracker
Fixed
Fixed in 1.1.6
Votes
0
Found in [Package]
1.1.4
Issue ID
AVPB-438
Regression
Yes
[VisionOS] Using an Image component with an Atlassed Sprite assigned causes ArgumentNullException
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Set the Sprite Packer Mode to “Sprite Atlas V2 - Enabled“ (Edit > Project Settings > Editor > Sprite Packer)
4. Enter the Play Mode
5. Observe the Console
Expected result: Only “SpriteAtlasManager.atlasRequested wasn't listened to while SpriteAtlas requested.“ warning is presen
Actual result: “[Diagnostics] EXCEPTION ArgumentNullException in PolySpatialCore“ and multiple “ArgumentNullException: Value cannot be null.“ errors are logged in addition to the warning
Reproducible with: 1.1.4 (2022.3.22f1)
Not reproducible with: 1.0.3 (2022.3.22f1)
Reproducible on: M1 MacOS 14.3.1
Not reproducible on: No other environment tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.1.6):
This will be fixed in the next bugfix release.