Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.0
Issue ID
MARS-1035
Regression
No
[MARS][Android] Overlay spawned after doing image recognition keeps snapping out of place when device is moved
Repro steps:
1. Open project "FilterFrames"
2. Build and Run on Android
3. Open the image "broyak.jpeg"
4. Scan the image with your device
5. Move the device around as in the video
Actual: The overlay detaches and keeps snapping back in different directions
Expected: The overlay stays in place
Reproducible with: 2020.3.9f1, 2021.1.6f1, 2021.2.0a17
Couldn't test 2019.4
Tested and reproduced on these devices:
Google Pixel 3 XL (Pixel 3 XL), Android 11, CPU: NOT FOUND, 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
Wasn't able to test iOS
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
Resolution Note:
Tracking issues seem to be coming directly from ARCore - verified by observing similar behavior in Google's ARCore sample.