Search Issue Tracker

Third Party Issue

Votes

0

Found in

2020.3.40f1

2021.3.12f1

2022.1.20f1

2022.2.0b11

2023.1.0a15

Issue ID

UUM-16961

Regression

No

[ChromeOS][Android] Build is not launching with Build and Run when Build Apple Bundle or Split Binary settings are selected

--

-

Steps to reproduce:
# Open the attached "PixelBookTest.zip" project
# In File > Build Settings enable _Build Apple Bundle (Google Play)_
# Build and Run for Android
# Observe the Console

Expected result: The message that Build is successful is visible in the Console and the Build is launched in the device
Actual result: The message that Build is successful is visible in the Console, but the Build fails to launch in the device, error messages are visible in the Console:
{code:java}
Installation failed with the following output:
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8

DeploymentOperationFailedException: Installation failed. See the Console for details.

UnityException: Could not find any valid targets to launch on for Android
{code}
Reproducible with: 2020.3.40f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b11, 2023.1.0a15

Notes:
- Reproducible with ARMv7, ARM64, x86 (Chrome OS), and x86-64 (Chrome OS) Target Architectures
- Build launch on the device also fails when _Split Application Binary_ is enabled in Edit > Project Settings > Publishing Settings but with different errors:
{code:java}
CommandInvokationFailure: Unable to create directory on phone. Please make sure the Android SDK is installed and is properly configured in the Editor.

DeploymentOperationFailedException: Failed pushing OBB file to the device. See the Console for details.

UnityException: Could not find any valid targets to launch on for Android
{code}

- Build launch doesn't fail if Build Apple Bundle (Google Play) and Split Application Binary settings are disabled
- Build works after opening it manually

Reproducible with devices:
VLNQA00465 - Google Pixelbook (Google Pixelbook), CPU: Amber Lake-Y / Kaby Lake-U/Y, GPU: virgl (Mesa DRI Intel(R) HD Graphics 615 (KBL GT2)), OS: 11

Not reproducible with devices:

- HP Chromebook 14a G5, Laptop, 102.0.5005.75 (64 bit), Android version 9, Build number: R102-14695.85.0
VLNQA00104 - LGE Nexus 5 (Nexus 5), CPU: Snapdragon 800 MSM8974, GPU: Adreno 330, OS: 6.0.1
VLNQA00133 - Google Pixel (Pixel), CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno 530, OS: 8.1.0
VLNQA00467 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 11
VLNQA00323 - Galaxy Note 10 USA (SM-N970U), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9.0.0
VLNQA00266 - Xiaomi Mi A2 (Mi A2), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0

  1. Resolution Note:

    This issue is related to permission and Google is handling it.
    This issue should be resolved in ChromeOS version M119 or higher.

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.