Search Issue Tracker
By Design
By Design in 6000.0.X
Votes
0
Found in
2022.3.8f1
2023.1.10f1
2023.2.0b8
2023.3.0a5
6000.0.0b11
Issue ID
UUM-48739
Regression
Yes
[Android] UnityEngine.UIElements.UQueryExtensions.Q causes an ArgumentNullException when External Dependencies are resolved
Reproduction steps:
1. Open the attached project “ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Download Firebase Unity SDK from the official page (https://firebase.google.com/docs/unity/setup ) and import "FirebaseAnalytics" and "FirebaseCrashlytics"
4. Go to [Assets] -> [External Dependency Manager] -> [Android Resolver] in the toolbar and perform "Force Resolve"
5. After confirming that all the above steps are completed, close Unity, then reopen it.
6. Observe the Console window
Expected result: No errors
Actual result: Error 'ArgumentNullException: Value cannot be null“ is thrown
Reproducible with: 2022.1.0a15, 2022.3.8f1, 2023.1.10f1, 2023.2.0b8, 2023.3.0a5
Not reproducible with: 2021.3.30f1, 2022.1.0a14
Reproducible on: Windows 10 Enterprise 21H2 (Android Platform)
Not reproducible on: Windows 10 Enterprise 21H2 (Windows Standalone Platform)
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:
The package was calling an extension method on a null value. The behavior is as designed for the UI toolkit part and the fix will land in the package separately from this issue.
Resolution Note (6000.0.X):
The package was calling an extension method on a null value. The behavior is as designed for the UI toolkit part and the fix will land in the package separately from this issue.