Application install fails when running tests from test module and abi splits are defined [285398001]

In Progress

Bug

Status Update

No update yet.

Description

ma...@google.com

created issue #1

Jun 1, 2023 09:19PM

It seems that when splits are specified in the application build gradle, the tested app apk is not chosen correctly according to the device abi.

Example of splits:

splits {
  abi {
    isEnable = true
    reset()
    include("x86", "x86_64", "armeabi-v7a", "arm64-v8a")
    isUniversalApk = true
  }
}

The application module exposes a single configuration per variant with all the apks, split per abi. It seems the test module chooses the wrong one. This doesn't seem to happen when running the tests with Android Studio.

Failure log:

Message: Failed to install APK(s): .../benchmarkRelease/baselineprofile-consumer-x86_64-benchmarkRelease.apk
        at com.android.tools.utp.plugins.deviceprovider.ddmlib.DdmlibAndroidDeviceController$executeAsync$deferred$1.invokeSuspend(DdmlibAndroidDeviceController.kt:223)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
Caused by: com.android.ddmlib.InstallException: INSTALL_FAILED_NO_MATCHING_ABIS: INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113
        at com.android.ddmlib.internal.DeviceImpl.installRemotePackage(DeviceImpl.java:1389)
        at com.android.ddmlib.internal.DeviceImpl.installPackage(DeviceImpl.java:1215)
        at com.android.tools.utp.plugins.deviceprovider.ddmlib.DdmlibAndroidDevice.installPackage(DdmlibAndroidDevice.kt)
        at com.android.tools.utp.plugins.deviceprovider.ddmlib.DdmlibAndroidDeviceController$executeAsync$deferred$1.invokeSuspend(DdmlibAndroidDeviceController.kt:192)
        ... 6 more

Note that the apk being installed is baselineprofile-consumer-x86_64-benchmarkRelease.apk when the device abi is arm64-v8a.

Comments

ma...@google.com <ma...@google.com> Jun 1, 2023 09:26PM

Accepted by ma...@google.com.

ma...@google.com <ma...@google.com> #2Jul 17, 2023 09:33PM

Assigned to bu...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Expected output
What is the expected output?

Current output
What is the current output?

bu...@google.com <bu...@google.com> #3Jul 17, 2023 09:33PM

Accepted by bu...@google.com.

How can you possibly need more information, i just told you the exact part of code causing the issue, and the code changes required to fix it!
Please read the description.

Expected output:
What is the expected output?
See attached "expected.webm" video in OP

Current output
What is the current output?
See attached "actual.webm" video in OP

ma...@google.com <ma...@google.com> #4May 28, 2024 05:24PM

Assigned to bu...@google.com.

1. Import attached project
2. Install and run on Android 5 (Lollipop) or above
3. Click FAB and see it fall below/behind the navigation bar once the Snackbar disappear

bu...@google.com <bu...@google.com> #5May 28, 2024 05:25PM

Accepted by bu...@google.com.

Could you please check the attached project as we couldn't extract the files from it.

mi...@google.com <mi...@google.com> #6May 31, 2024 08:30PM

It's a RAR archive, there's no issue with it.
However you have problems extracting such, here's the same content as a ZIP archive.

ma...@google.com <ma...@google.com> #7May 31, 2024 08:43PM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

mi...@google.com <mi...@google.com> #8Jun 12, 2024 09:50PM

@ coordinator layout,

Please check this issue and provide your inputs.