Search Issue Tracker
In Progress
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
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [VFX] Missing Expand Toggle with Output Slot
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Resolution Note:
This will be fixed in the next bugfix release.