Search Issue Tracker

Fixed

Fixed in 7.1.2

Votes

12

Found in [Package]

7.0.0

Issue ID

MXPB-17

Regression

No

[Android] Black screen with skipped rendering frame and error "GfxDevice is in invalid state (device lost)" when Player is built with Google ARCore

Package: Magic Leap XR Plugin

-

Reproduction steps:
1. Open the attached project "ReproProj" with Android Platform
2. Open the “/Assets/ExampleAssets/Scenes/SampleScene.unity” Scene
3. Build And Run
4. Observe the Player

Expected result: The screen shows a view from the back camera of the device
Actual result: The screen is black

Reproducible with: 5.0.6 (2023.1.5f1), 5.1.0-pre.9 (2022.3.4f1, 2023.1.5f1, 2023.2.0a23)
Could not test with: 5.1.0-pre.9 (2021.3.28f1) (An error occurred while resolving packages: Project has invalid dependencies: com.unity.feature.ar: Package [com.unity.feature.ar@1.0.1] cannot be found)

Reproducible with devices:
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS

Not reproducible with devices:
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76

Testing environment: Windows 10 Enterprise 21H2

Notes:
- Rotating the device or putting it into the background and opening it up again fixes the issue
- In LogCat message appears "Skipped rendering frame because GfxDevice is in invalid state (device lost)"
- Issue does not reproduce when com.unity.feature.ar package is removed

  1. Resolution Note (fix version 7.1.2):

    This issue is addressed when the latest version of the MagicLeap plugin is release (7.1.2)

Log in to vote on this issue

Comments (7)

  1. CiaranWills

    Dec 21, 2023 02:36

    This appears to be an issue with the Magic Leap package that is installed as part of the 'AR' Feature in the package manager. If you remove the Magic Leap package (and you may need to remove the AR Feature first to unlock it) and delete your project's Library directory (this is important) this issue should be resolved.

  2. AlphaKilla

    Dec 17, 2023 23:53

    Same issue with unity 2023 and ar core 5.0.2

  3. wilcoboode

    Dec 11, 2023 09:54

    Same issue
    Quest 3 (firmware 59.0), OpenXR Meta 1.0.1, OpenXR 1.9.1, Unity 2022.3.12f1, XR Interaction Toolkit 2.5.2

  4. AceSunshine

    Nov 23, 2023 15:24

    same problem
    Unity 2022.3.6f1
    Device: oppo a5s

  5. gtk2k

    Nov 22, 2023 02:28

    same problem
    Unity 2022.3.11f1
    Device: ROG5

  6. LeoMH

    Aug 29, 2023 15:17

    Yeah same problem here with Samsung Galaxy Tab S6 Lite

  7. MaDMath03

    Aug 28, 2023 15:20

    I was able to reproduce this using unity 2022.3.6f1, 2022.3.2f1 and 2023.1.8f1. It seems to a problem with ARFoundation since versions prior to 5.0 used to work correctly.

    I've been trying to build the default AR project for Android on multiple Android devices but the issue prevented me from using the Unity 2022+ versions.

    The build asks for camera access then displays a balck screen, LogCat displays the following error :
    Error GET ged_gpu timestamp: GED_ERROR_FAIL wEre = 0, -2

    Device tested :
    Samsung Galaxy Tab S5e, Android 11, CPU : Qualcomm SDM670, GPU : Adreno 615
    Samsung Galaxy Tab A8, Android 13, CPU : Unisoc Tiger T618, GPU : Mali G52 MP2
    Lenovo Tab P11 Gen 2, Android 12, CPU : Mediatek MT8781 Helio G99, GPU : Mali-G57 MC2
    Samsung Galaxy A32, Android 11, CPU : Mediatek MT6769V/CU Helio G80, GPU : Mali-G52 MC2

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues