"error loading build artifacts from" when trying to deploy a preview on Koala Canary 4 [333408171]

Fixed

Bug

Status Update

No update yet.

Description

va...@gmail.com

created issue #1

Apr 9, 2024 10:14AM

DESCRIBE THE ISSUE IN DETAIL: Android studio is unable to deploy previews and fails with an error Error loading build artifacts from: ./feature/profile/build/intermediates/apk_ide_redirect_file/debugAndroidTest/createDebugAndroidTestApkListingFileRedirect/redirect.txt

STEPS TO REPRODUCE:

Install Koala Canary 4 (not repro on Canary 3)
Try to run a composable preview in a multi-module project
Preview will not run, 100% repro rate

Repro on both phyical device and an emulator. Previews display normally in the IDE

ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)

2024-04-09 13:10:25,536 [2967709]   INFO - Emulator: Small Phone API 28 - Booted notification event: booted { time: 1915 }
2024-04-09 13:10:25,537 [2967710]   INFO - Emulator: Small Phone API 28 - Successfully loaded snapshot 'default_boot'
2024-04-09 13:10:25,537 [2967710]   INFO - Emulator: Small Phone API 28 - OpenGL Vendor=[Google (Apple)]
2024-04-09 13:10:25,537 [2967710]   INFO - Emulator: Small Phone API 28 - OpenGL Renderer=[Android Emulator OpenGL ES Translator (Apple M1 Pro)]
2024-04-09 13:10:25,537 [2967710]   INFO - Emulator: Small Phone API 28 - OpenGL Version=[OpenGL ES 3.0 (4.1 Metal - 88)]
2024-04-09 13:10:25,539 [2967712]   INFO - #com.android.tools.idea.streaming.emulator.EmulatorView - Received notification: 5: { 1: 1915 }
2024-04-09 13:10:25,579 [2967752]   INFO - #com.android.tools.idea.adb.AdbService - Device [emulator-5554] has come online
2024-04-09 13:10:25,621 [2967794]   INFO - #com.android.tools.idea.run.AndroidRunConfigurationExecutor - Launching on device Small_Phone_API_28 [emulator-5554]
2024-04-09 13:10:25,621 [2967794]   INFO - #c.i.e.r.ExecutionUtil - Error running 'OwnProfileScreenPreview - OwnProfile (state 1)':<br>Error loading build artifacts from: /feature/profile/build/intermediates/apk_ide_redirect_file/debugAndroidTest/createDebugAndroidTestApkListingFileRedirect/redirect.txt
com.intellij.execution.ExecutionException: Error loading build artifacts from: /feature/profile/build/intermediates/apk_ide_redirect_file/debugAndroidTest/createDebugAndroidTestApkListingFileRedirect/redirect.txt
	at com.android.tools.idea.run.AndroidRunConfigurationExecutor.apkInfosSafe(AndroidRunConfigurationExecutor.kt:428)
	at com.android.tools.idea.run.AndroidRunConfigurationExecutor.access$apkInfosSafe(AndroidRunConfigurationExecutor.kt:78)
	at com.android.tools.idea.run.AndroidRunConfigurationExecutor$run$1$3$1.invokeSuspend(AndroidRunConfigurationExecutor.kt:129)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:280)
	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:85)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59)
	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)
	at com.intellij.openapi.progress.CoroutinesKt$runBlockingCancellable$1.invoke(coroutines.kt:132)
	at com.intellij.openapi.progress.CoroutinesKt$runBlockingCancellable$1.invoke(coroutines.kt:126)
	at com.intellij.openapi.progress.ContextKt.prepareIndicatorThreadContext$lambda$5(context.kt:107)
	at com.intellij.openapi.progress.impl.CoreProgressManager.silenceGlobalIndicator(CoreProgressManager.java:1022)
	at com.intellij.openapi.progress.ContextKt.prepareIndicatorThreadContext(context.kt:105)
	at com.intellij.openapi.progress.ContextKt.prepareThreadContext(context.kt:75)
	at com.intellij.openapi.progress.CoroutinesKt.runBlockingCancellable(coroutines.kt:126)
	at com.intellij.openapi.progress.CoroutinesKt.runBlockingCancellable(coroutines.kt:121)
	at com.android.tools.idea.run.AndroidRunConfigurationExecutor.run(AndroidRunConfigurationExecutor.kt:95)
	at com.android.tools.idea.execution.common.AndroidConfigurationExecutorRunProfileState.run(AndroidConfigurationExecutor.kt)
	at com.android.tools.idea.run.DefaultStudioProgramRunner.run(DefaultStudioProgramRunner.kt:102)
	at com.android.tools.idea.execution.common.AndroidConfigurationProgramRunner$execute$5.run(AndroidConfigurationProgramRunner.kt:126)
	at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:477)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:133)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsynchronously$6(CoreProgressManager.java:528)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:250)
	at com.intellij.openapi.progress.ProgressManager.lambda$runProcess$0(ProgressManager.java:100)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$1(CoreProgressManager.java:221)
	at com.intellij.platform.diagnostic.telemetry.helpers.TraceKt.use(trace.kt:46)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:220)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:660)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:735)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:691)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:659)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:79)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:202)
	at com.intellij.openapi.progress.ProgressManager.runProcess(ProgressManager.java:100)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$5(ProgressRunner.java:250)
	at com.intellij.openapi.progress.impl.ProgressRunner$ProgressRunnable.run(ProgressRunner.java:500)
	at com.intellij.util.concurrency.ChildContext$runAsCoroutine$1.invoke(propagation.kt:81)
	at com.intellij.util.concurrency.ChildContext$runAsCoroutine$1.invoke(propagation.kt:81)
	at com.intellij.util.concurrency.ChildContext.runAsCoroutine(propagation.kt:86)
	at com.intellij.util.concurrency.ChildContext.runAsCoroutine(propagation.kt:81)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$launchTask$18(ProgressRunner.java:466)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Unknown Source)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: com.android.tools.idea.run.ApkProvisionException: Error loading build artifacts from: /feature/profile/build/intermediates/apk_ide_redirect_file/debugAndroidTest/createDebugAndroidTestApkListingFileRedirect/redirect.txt
	at com.android.tools.idea.run.GradleApkProvider.getApkFromBuildOutputFile(GradleApkProvider.java:489)
	at com.android.tools.idea.run.GradleApkProvider.getApk(GradleApkProvider.java:467)
	at com.android.tools.idea.run.GradleApkProvider.getApks(GradleApkProvider.java:306)
	at com.android.tools.idea.run.GradleApkProvider.getApks(GradleApkProvider.java:164)
	at com.android.tools.idea.run.AndroidRunConfigurationExecutor.apkInfosSafe(AndroidRunConfigurationExecutor.kt:426)
	... 49 more

Build #AI-241.14494.158.2411.11678081, built on April 5, 2024 Runtime version: 17.0.10+0-17.0.10b1087.21-11609105 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

Version of Gradle Plugin: 8.3.1 Version of Gradle: 8.7 Version of Java: 21 OS: MacOS Sonoma 14.1.1

Comments

am...@google.com <am...@google.com> Apr 15, 2024 11:35AM

Assigned to am...@google.com.

am...@google.com <am...@google.com> Apr 17, 2024 08:26AM

Reassigned to ls...@google.com.

am...@google.com <am...@google.com> #2May 3, 2024 01:26PM

Yigit, I haven't had time to try reproducing yet, but they have a github link which is nice. What's weird though is I don't think anything has changed recently at all, but maybe you're aware? Although, looking at the callstack, it may be an AGP issue? If it looks like that to you too, bounce it back to me.

OP: Was this a regression? And just to make sure, when you say "run ./gradlew help", you're seeing this from the command line? Or from within Studio?

va...@gmail.com <va...@gmail.com> #3May 3, 2024 01:27PM

I'm seeing this from command line.

Yes this seems to be a regression starting from 7.0.0-alpha10.

Note that the project I linked doesn't use databinding at all, enabling the build config flag is all that's needed to reproduce this.

yo...@gmail.com <yo...@gmail.com> #4Jun 2, 2024 11:57PM

Thanks for the quick reply. I have a short open window right now so I'll try to repro and see if I can figure out which component this is best for.

Message last modified on Jun 2, 2024 11:58PM

ba...@gmail.com <ba...@gmail.com> #5Jun 4, 2024 08:16PM

I can repro what OP is seeing. It may be tempting to move this to the data binding component but this seems more like an AGP change. I don't believe the data binding compiler has been changed recently, around the time AGP 7.0.0-alpha10 went out.

am...@google.com <am...@google.com> #6Jun 5, 2024 11:49AM

Also, slightly more direct steps (although it amounts to the same thing as what's in comment #1)

Sync the github project somewhere (git clone https://github.com/ReactiveCircus/streamlined.git)
Double check everything's working as expected (./gradlew help should work)
Edit app/build.gradle.kts: Search for buildFeatures and add dataBinding = true as the first entry, above buildConfig
Now, things are expected to break (./gradlew help should throw an exception)
Edit buildSrc/src/main/kotlin/io/github/reactivecircus/streamlined/Dependencies.kt: change the AGP version to 7.0.0-alpha09
Now, things are expected to work again(./gradle help should work)

ba...@gmail.com <ba...@gmail.com> #7Jun 9, 2024 11:28PM

yea this seems unrelated to data binding as we didn't change data binding itself

There were some resource related changes so cc'ing Iza in case they might be related but i don't think so. This seems like a lifecycle issue.

pa...@gmail.com <pa...@gmail.com> #8Jun 10, 2024 09:38AM

HI there, I saw this last week, it looked like kapt was trying to resolve attributes at configuration time, resulting in this error, however I've only seen this when non-transitive R was enabled.
I'll look more into this, thanks for the detailed description and repro case!

Message last modified on Jun 11, 2024 06:31AM

ba...@gmail.com <ba...@gmail.com> #9Jun 10, 2024 04:41PM

It does indeed look like kapt is resolving attributes at configuration time, and has been for a while. The only reason this only came up now is that resolving single files or directories at config time was passing (while incorrect), but adding the new attribute that's a file collection - it actually blows up now. We've seen a few reports in the past where changed xml files didn't result in updated data binding files, which is also explained by the config time resolution.
This affects even 1.50-M1 kotlin, and the code resolving the attributes is here:

https://github.com/JetBrains/kotlin/blob/master/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/internal/kapt/Kapt3KotlinGradleSubplugin.kt#L354

As a workaround to get data binding working, I'll add a new task that merges dependencies R.txt files into one, and then pass that single file to kapt/db. So while the incorrect resolving will still be there while jetbrains fixes this issue, it will allow the non-transitive R + data binding builds to succeed.

am...@google.com <am...@google.com> #10Jun 12, 2024 02:35PM

Marked as fixed, reassigned to am...@google.com.

nice find!

There is actually another issue about incremental compilation, do you think they might be related to the other issue you've mentioned?

https://buganizer.corp.google.com/issues/182682213

an...@google.com <an...@google.com> #11Jun 17, 2024 07:32PM

@10 It's likely, however it also seems to happen on clean builds (but perhaps it fails because of caching?). It's possible they are related. KAPT resolves the attributes at configuration time, effectively messing up any dependencies, so it could potentially manifest in this way too.

to...@fitbod.me <to...@fitbod.me> #12Nov 13, 2024 11:35PM

I've uploaded https://github.com/JetBrains/kotlin/pull/4238 to fix this in KAPT.

Message last modified on Nov 13, 2024 11:44PM

ni...@gmail.com <ni...@gmail.com> #13Nov 18, 2024 03:14PM

This affects even 1.50-M1 kotlin, and the code resolving the attributes is here: https://github.com/JetBrains/kotlin/blob/master/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/internal/kapt/Kapt3KotlinGradleSubplugin.kt#L354

This is similar to/the same as https://youtrack.jetbrains.com/issue/KT-39715.

Regarding Issue 182682213, it is too ambiguous at this point, so I'll just debug that issue separately (and keeping this bug in mind).

cy...@gmail.com <cy...@gmail.com> #14Nov 19, 2024 10:31AM

This has now been fixed in master, and should be included in the future releases of 7.0. Thank you again for reporting the issue!

am...@google.com <am...@google.com> #15Nov 19, 2024 01:43PM

Thanks! Do we know if this is going to be included in the next canary (or one after that)? It's been blocking us from updating AGP / Studio for 4 releases now so I'd really love to get back to the bleeding edge soon:)

ch...@gmail.com <ch...@gmail.com> #16Nov 19, 2024 03:53PM

It should be included in Beta 1.

lu...@mindbodyonline.com <lu...@mindbodyonline.com> #17Nov 20, 2024 06:13PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Chipmunk Canary 2 (2021.2.1.2)
Android Gradle Plugin 7.2.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

ks...@letsenvision.com <ks...@letsenvision.com> #18Nov 22, 2024 02:25PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Bumblebee Beta 2 (2021.1.1.15)
Android Gradle Plugin 7.1.0-beta02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

jo...@gmail.com <jo...@gmail.com> #19Jan 3, 2025 01:24PM

The fixes for this issue are now also available in:

Android Studio Koala Feature Drop | 2024.1.2 Canary 1
Android Gradle Plugin 8.6.0-alpha01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Message last modified on Jan 3, 2025 01:24PM

mi...@gmail.com <mi...@gmail.com> #20Jan 6, 2025 01:18PM

still getting this on meerkat canary 7, initially I got this issue while Build->Clean, but #cpmment17 fixes this issue

Message last modified on Jan 6, 2025 01:22PM

am...@google.com <am...@google.com> #21Jan 6, 2025 01:26PM

For people getting this:

Can you please provide a sample project in which you can reproduce this issue? I can no longer reproduce it in nowinandroid, as suggested in comment #4
Does the workaround suggested in comment #17 work for you?

Thanks!

al...@phoops.it <al...@phoops.it> #22Feb 17, 2025 01:37PM

I confirm that the workaround suggested in comment #17 solved the issue for me. Thanks!

ar...@gmail.com <ar...@gmail.com> #23Mar 5, 2025 01:19AM

i just updated to meerkat and faced the same issue solved by

comment #17

di...@gmail.com <di...@gmail.com> #24Mar 5, 2025 09:33AM

I can also confirm that the fix suggested in comment #17 solves the issue.

ch...@itgri.ru <ch...@itgri.ru> #25Mar 11, 2025 05:43AM

I confirm that the fix suggested in

comment #17

solves the issue.

vi...@gmail.com <vi...@gmail.com> #26Mar 17, 2025 11:53AM

Reproduced on Meerkat 2024.3.1 and Meerkat 2024.3.2 Feature Drop Canary 8.

comment #17

resolves the issue.

Message last modified on Mar 17, 2025 11:54AM

bb...@gmail.com <bb...@gmail.com> #27Mar 18, 2025 03:21PM

Step by Step what need to do

Steps to Fix the Issue
Open Run/Debug Configurations:
In Android Studio, go to the top menu and click Run > Edit Configurations.
Alternatively, click the dropdown next to the "Run" button in the toolbar (it shows your current run configuration, e.g., app), then select Edit Configurations.
Select Your Run Configuration:
In the left panel, find your run configuration (e.g., app under "Android App"). Click it to edit it.
If you’re unsure which one is active, it’s usually the one selected in the toolbar when you hit "Run" or "Debug."
Add "Gradle-aware Make" to Before Launch:
Scroll down to the Before Launch section at the bottom of the configuration window. This section lists tasks that run before your app launches.
If "Gradle-aware Make" isn’t already listed, click the + (Add) button.
From the dropdown, select Gradle-aware Make.
If you don’t see it, ensure your project is synced with Gradle (click Sync Project with Gradle Files in the toolbar first).
Apply and Save:
Click Apply, then OK to save the changes and close the dialog.
Run Your Project:
Try running your app again by clicking the Run (green triangle) or Debug (bug icon) button in the toolbar.
"Gradle-aware Make" ensures Gradle builds the necessary artifacts (e.g., APK) before launching, which might resolve the redirect.txt error.

Screenshot 2025-03-18 at 15.20.08.png

105 KB

View

Download

Issue 333408171

Description

Issue summary

Comments

am...@google.com <am...@google.com> Apr 15, 2024 11:35AM

am...@google.com <am...@google.com> Apr 17, 2024 08:26AM

am...@google.com <am...@google.com> #2May 3, 2024 01:26PM

va...@gmail.com <va...@gmail.com> #3May 3, 2024 01:27PM

yo...@gmail.com <yo...@gmail.com> #4Jun 2, 2024 11:57PM

ba...@gmail.com <ba...@gmail.com> #5Jun 4, 2024 08:16PM

am...@google.com <am...@google.com> #6Jun 5, 2024 11:49AM

ba...@gmail.com <ba...@gmail.com> #7Jun 9, 2024 11:28PM

pa...@gmail.com <pa...@gmail.com> #8Jun 10, 2024 09:38AM

ba...@gmail.com <ba...@gmail.com> #9Jun 10, 2024 04:41PM

am...@google.com <am...@google.com> #10Jun 12, 2024 02:35PM

an...@google.com <an...@google.com> #11Jun 17, 2024 07:32PM

to...@fitbod.me <to...@fitbod.me> #12Nov 13, 2024 11:35PM

ni...@gmail.com <ni...@gmail.com> #13Nov 18, 2024 03:14PM

cy...@gmail.com <cy...@gmail.com> #14Nov 19, 2024 10:31AM

am...@google.com <am...@google.com> #15Nov 19, 2024 01:43PM

ch...@gmail.com <ch...@gmail.com> #16Nov 19, 2024 03:53PM

lu...@mindbodyonline.com <lu...@mindbodyonline.com> #17Nov 20, 2024 06:13PM

ks...@letsenvision.com <ks...@letsenvision.com> #18Nov 22, 2024 02:25PM

jo...@gmail.com <jo...@gmail.com> #19Jan 3, 2025 01:24PM

mi...@gmail.com <mi...@gmail.com> #20Jan 6, 2025 01:18PM

am...@google.com <am...@google.com> #21Jan 6, 2025 01:26PM

al...@phoops.it <al...@phoops.it> #22Feb 17, 2025 01:37PM

ar...@gmail.com <ar...@gmail.com> #23Mar 5, 2025 01:19AM

di...@gmail.com <di...@gmail.com> #24Mar 5, 2025 09:33AM

ch...@itgri.ru <ch...@itgri.ru> #25Mar 11, 2025 05:43AM

vi...@gmail.com <vi...@gmail.com> #26Mar 17, 2025 11:53AM

bb...@gmail.com <bb...@gmail.com> #27Mar 18, 2025 03:21PM

Add comment

Issue metadata