Search Issue Tracker
Third Party Issue
Votes
1
Found in
6000.0.10f1
Issue ID
UUM-75606
Regression
No
[Quest] Crash with Error "JNI GetStaticFieldID called with pending exception java.lang.ClassNotFoundException: com.unity3d.player.UnityPlayer" when launching Player with Meta Core SDK on Quest
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 a Quest device
Expected result: The Player does not crash and continues to run
Actual result: Player crashes at launch
Reproducible with: 6000.0.10f1
Could not test with: 2021.3.40f1, 2022.3.36f1 (Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION: Failed to parse /data/app/vmdl1590677866.tmp/base.apk: AndroidManifest.xml])
Reproducible on:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Quest 3 (user reported)
Not reproducible on:
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- When making the AsyncInitialize call, the catch block never executes and neither does the OnComplete callback
Comments (1)
-
Flamacore
Aug 04, 2024 10:35
Experienceing the exact same issue with Unity 6000.0.7f1 as well.
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
Customer's issue was resolved by upgrading to newer version of the Meta Core SDK from the asset store
Resolution Note:
Customer's issue was resolved by upgrading to newer version of the Meta Core SDK from the asset store