Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.44f1
6000.0.16f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
Issue ID
UUM-78764
Regression
No
[Android] Null reference when using InstantiateAsync
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/test.unity” Scene
3. Switch to Android Platform
4. Build and Run on Quest
5. Observe the Player
Expected result: All Spheres are blue
Actual result: Some of the Spheres are red
Reproducible with: 2022.3.44f1, 6000.0.16f1
Could not test with: 2021.3.42f1 (The name 'InstantiateAsync' does not exist in the current context)
Reproducible on:
Windows Standalone Player
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Not reproducible on:
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Reproducible with OpenGLES3 and Vulkan
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
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.