Search Issue Tracker

Fixed

Votes

0

Found in [Package]

3.0.2

Issue ID

XRIT-162

Regression

No

[Quest 3] The Player crashes on "ArgumentNullException: Value cannot be null" when built with the XR Interaction Toolkit and a specific project

Package: XR Interaction Toolkit

-

Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Switch to Android Platform
4. Build and Run on Quest
5. In Player, press “Allow”

Expected result: The Player does not crash and continues to run
Actual result: Player crashes at launch

Reproducible with: 2.5.4 (2023.2.20f1), 3.0.0-pre.1 (2023.2.20f1), 3.0.3 (6000.0.4f1)
Could not test with: 3.0.3 (2021.3.39f1, 2022.3.31f1) (Package com.unity.xr.arfoundation@6.0.1 has invalid dependencies or related test packages: com.unity.ugui (dependency): Resolved version [1.0.0] does not satisfy requested version [2.0.0])

Reproducible on:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650

Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested

Note:
- Reproducible with New Input System and Old Input System

Comments (1)

  1. chris-massie

    Aug 01, 2024 20:10

    Current workaround is to unset Project-wide Actions and instead use a component like Input Action Manager to enable the Input Action Asset instead. That component will enable the actions during OnEnable, which is after the custom composite bindings, interactions, and processors in the package registers them with Input System. Currently when the Project-wide Actions are set, the actions will be enabled by Input System before the definitions can be registered, causing the errors.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.