Search Issue Tracker
Fixed
Fixed in 2.0.0-pre.11
Votes
1
Found in [Package]
1.3.1
2.0.0-pre.11
Issue ID
AVPB-776
Regression
No
PolySpatial uses wrong path to read boot.config resulting in an error on launch when building to Android
Steps to reproduce:
1. Open the attached user's project "MR_AndroidTest.zip"
2. Switch to Android
3. Build to an Android device
4. Observe the error in Android Logcat
Expected results: no error in Android Logcat when launching a build with Polyspatial on Android
Actual results: PolySpatial uses wrong path to read boot.config resulting in an error on launch when building to Android
Reproducible with: Polyspatial 1.3.1 - 2.0.0-pre.11 (6000.0.16f1)
Could not test on 2021.3.43f1 and 2022.3.43f1 due to Android resource linking failure when performing a build
Reproducible with these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12
VLNQA00422 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 11
VLNQA00528 - HMD Global Nokia G20 (Nokia G20), CPU: Mediatek MT6765G Helio G35 (12 nm), GPU: PowerVR Rogue GE8320, OS: 13
VLNQA00423 - Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 9
VLNQA00381 - Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4, OS: 9
Testing Environment: Windows 11 23H2
Not reproducible on: no other environment tested
Notes:
-Android Logcat error:
Error Unity Unity.PolySpatial.Internals.BootConfigUtility:ReadBootConfig(String)
Unity Unity.PolySpatial.Internals.<>c:<.cctor>b__11_0()
Unity Unity.PolySpatial.Internals.PolySpatialCore:GetShouldEnablePolySpatialRuntimeAtRuntime(Boolean&)
Unity Unity.PolySpatial.Internals.PolySpatialCore:get_RuntimeEnabled()
Unity.PolySpatial.Internals.BootConfigUtility.ReadBootConfig (System.String bootConfigPath) [0x00000] in <00000000000000000000000000000000>:0
Unity.PolySpatial.Internals.BootConfigUtility+<>c.<.cctor>b__11_0 () [0x00000] in <00000000000000000000000000000000>:0
Unity.PolySpatial.Internals.PolySpatialCore.GetShouldEnablePolySpatialRuntimeAtRuntime (System.Boolean& enabled) [0x00000] in <00000000000000000000000000000000>:0
Unity.PolySpatial.Internals.BootConfigUtility.ReadBootConfig (System.String bootConfigPath) [0x00000] in <00000000000000000000000000000000>:0
Unity.PolySpatial.Internals.BootConfigUtility+<>c.<.cctor>b__11_0 () [0x00000] in <00000000000000000000000000000000>:0
Unity.PolySpatial.Internals.PolySpatialCore.GetShouldEnablePolySpatialRuntimeAtRuntime (System.Boolean& enabled) [0x00000] in <00000000000000000000000000000000>:0
Unity.PolySpatial.Internals.BootConfigUtility.ReadBootConfig (System.String bootConfigPath) [0x00000] in <00000000000000000000000000000000>:0
Unity.PolySpatial.Internals.BootConfigUtility+<>c.<.cctor>b__11_0 () [0x00000] in <00000000000000000000000000000000>:0
Unity.PolySpatial.Internals.PolySpatialCore.GetShouldEnablePolySpatialRuntimeAtRuntime (System.Boolean& enabled) [0x00000] in <00000000000000000000000000000000>:0
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
PolySpatial does not currently support any platform except visionOS. We noted you are interested in building for Android but unfortunately this is not available for Android platforms at this time.
Resolution Note (fix version 2.0.0-pre.11):
PolySpatial does not currently support any platform except visionOS. We noted you are interested in building for Android but unfortunately this is not available for Android platforms at this time.