Search Issue Tracker
Fixed in arfoundation 5.0.0-pre.1, 4.2.0-pre.11
Votes
6
Found in [Package]
4.1.7
Issue ID
1337758
Regression
No
[ARFoundation][ARCore][Android][IL2CPP] Runtime crash when initializing MutableRuntimeReferenceImageLibrary
Repro steps:
1. Open attached project "arfoundation-demos-master"
2. Build and Run the "imageTrackingStaticRuntimeSet" scene to Android
3. Start scanning a plane
Actual: App crashes
Expected: App doesn't crash
Reproducible with: 2019.4.16f1, 2020.3.11f1, 2021.1.9f1, 2021.2.0a17
Tested and reproduced on these devices:
Google Pixel 3 XL (Pixel 3 XL), Android 11, CPU: Snapdragon 845, GPU: Adreno (TM) 630
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
Notes:
- Doesn't seem to crash with development builds
- Doesn't seem to crash on Mono
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
BrentScopeAR
Jul 09, 2021 15:51
Any intentions to fix this for AR Foundation 4.1? We are still on Unity 2019 and upgrading to Unity 2020 so we can use ARFoundation 4.2 is something we are hoping to avoid.
Fingers crossed this fix is ported down to 4.1. :-D