Search Issue Tracker
Active
Under Consideration for 2.6.X, 3.0.X
Votes
0
Found in [Package]
2.6.3
3.0.5
Issue ID
XRIT-189
Regression
No
Spawned objects move after screen sleep on Android
*Steps to reproduce:*
0. Set your Android phone display to sleep after 30 or 60 seconds.
1. Use Unity 2023.2 to create a new project using AR mobile Template 2.0.
2. Build and Run on an AR-capable Android phone.
3. Point your phone camera North; follow the prompts in the Welcome UI to scan planes and place objects at the North end of the room.
4. Continue pointing your phone North and do nothing until the screen sleeps.
5. Point your phone East; wake up the display.
*Actual results:*
The objects that should be in the North are now in the East (or wherever your camera pointed when you woke up the screen after sleep). If you turn your phone North then the objects might jump to their original places, but if you look East again then the objects will jump there. Basically ARCore seems confused about where the objects should be.
*Expected results:*
Spawned objects should remain in their original places after the screen sleeps and re-awakens.
*Reproducible with versions:*
Google Pixel 7 Pro and Samsung 23 Ultra
Unity 2023.2.10f1
com.unity.template.ar-mobile (Branch: release/2023.2, Commit: 6acf70d6)
*Not reproducible with versions:*
iPhone 13
Unity 2023.2.10f1
com.unity.template.ar-mobile (Branch: release/2023.2, Commit: 6acf70d6)
*Can’t test with versions:*
*Tested on (OS):*
iOS and Android, deployed from Editor on MacOS.
*Notes:*
* User Prevalence set as majority because I heard that Android install base is huge. Feel free to retort if you have seen statistics favoring iOS. I did not flag this as a regression, though I did not test this specific case for 1.0. Contact me if follow-up testing would help solve this bug.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Add comment