"Operation Succeeded" in Android Studio 4.1, with no action

Question

Have anyone faced this issue with the new Android Studio 4.1. When I run the app to the simulator, everything works and builds. Later it also shows a message

In the run, the error message is

Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: Error loading build artifacts from: LOCATION/build/outputs/apk/act/debug/output-metadata.json

'Invalidate Caches/Restart' worked with me on gradle version 4.1.0 — Ashwin Nirmale, Dec 31 '20 at 04:29

score 49 · Answer 1 · answered Dec 31 '20 at 02:12

49

I see this when switching branches from one that uses Android Gradle Plugin 4.0.1 and Gradle 6.1.1 to one that uses Android Gradle Plugin 4.1.1 and Gradle 6.5.

The workaround here is to manually run File > Sync Project with Gradle Files.

answered Dec 31 '20 at 02:12

CommonsWare

986,068
189
2,389
2,491

Thanks a lot. It's working like charm after sync project with Gradle files. – sudharsan chandrasekaran Aug 01 '22 at 06:25
Hi CommonsWare, I tried all the work around provided here - https://stackoverflow.com/questions/56440572/how-to-fix-unable-to-determine-application-id-com-android-tools-idea-run-apkpr .... For me none of the solutions worked. I am still looking for solution. Also I have mentioned in one of the answer the strange behaviour observed with respect to issue. – Shadow Droid Jan 10 '23 at 05:46

sadat · Accepted Answer · 2021-03-16T02:24:59.110

20

I just figured out that, if you upgrade your gradle in one branch and change your branch to something which had the old gradle, you may face this issue.

I just updated the gradle and it fixed the issue.For me I change from

classpath 'com.android.tools.build:gradle:4.0.1'

to

classpath 'com.android.tools.build:gradle:4.1.2'

edited Mar 16 '21 at 02:24

answered Oct 22 '20 at 04:19

sadat

4,004
2
29
49

10

this does not help – John Deer Nov 12 '20 at 12:51
1

currently, its 4.1.1 – sadat Nov 13 '20 at 00:32
sure, i mean it still pops up and stays forever, even on most recent plugin versions – John Deer Nov 13 '20 at 00:59
1

basically my problem was that the app was not really pushed to the emulator. – sadat Nov 13 '20 at 02:18
1

This does not work. any solution for 4.1.1 version? – Mehta Dec 01 '20 at 10:11
It doesn't help me at all. Any solutions guys? I have updated to 4.1.1 but same issue both with Emulator and Physical device. – Maulik Dodia Jan 07 '21 at 08:41
I have com.android.tools.build:gradle:4.1.3 and it´s not working – Jorgesys Sep 13 '21 at 17:40
1

@JohnDeer try another version of android studio – Kochchy Feb 16 '23 at 15:26

score 6 · Answer 3 · answered Sep 13 '21 at 18:17

Changing o updating your gradle version is not the real solution.

classpath 'com.android.tools.build:gradle:5.?.?'

if you change the value this is provoking a new project sync with the files of your project.

so the real solution is to synchronize the project with the Gradle files:

File > Sync Project with Gradle Files.

score 3 · Answer 4 · answered Jan 01 '21 at 18:09

3

This fixed my issue. Go to

Run > Edit Configurations > Android App > app

On General tab change Launch option to

Default Activity

In my case it was selected

Nothing

answered Jan 01 '21 at 18:09

mDonmez

400
4
14

score 3 · Answer 5 · answered Jan 25 '22 at 10:56

3

I met with this issue when I manually copied some files of one project into another(they were related to gradle).

So, In my case, the main issue was with the settings.gradle file. There is this line in the file:

rootProject.name = "Your App Name"

Make sure it is exactly similar to the home folder of your project.

answered Jan 25 '22 at 10:56

R. Rohilla

71
8

1

Exactly, when I cloned the project onto another computer, I created a new folder name, and as you said, when I changed it to match the folder name, it worked. Thanks. – Reejesh PK May 23 '23 at 04:19

score 2 · Answer 6 · answered Dec 10 '20 at 06:15

2

This is an issue of Gradle 4.1.1, Will work properly in Gradle 4.1.0, Please use :

classpath 'com.android.tools.build:gradle:4.1.0'

answered Dec 10 '20 at 06:15

Mital Joshi

1,132
1
11
15

score 1 · Answer 7 · answered May 18 '22 at 07:44

1

First Build->clean your project and then Build->Rebuild Project it will solve the problem

answered May 18 '22 at 07:44

Yazdan Ilyas

374
4
8

هيثم · Answer 8 · 2020-12-09T15:26:30.083

0

A possibility why This problem happens because of the run configuration. go to run configurations, within Before launch add Gradle-aware Make. It worked for me.

edited Dec 09 '20 at 15:26

answered Dec 08 '20 at 11:35

هيثم

791
8
11

score 0 · Answer 9 · answered Jan 19 '21 at 18:23

0

File/Invalidate Caches/Restart worked for me. Note: I already applied above mentioned solutions.

answered Jan 19 '21 at 18:23

shaby

1,301
1
15
17

score -1 · Answer 10 · answered Jan 27 '21 at 07:34

-1

I'm using RedMi android device, seems all the MI android phone should has this issue.

I tried all but doesn't work. The solution is turn off Turn on MIUI optimization in Developer options.

answered Jan 27 '21 at 07:34

William Hu

15,423
11
100
121

score -1 · Answer 11 · answered Jun 29 '21 at 11:22

-1

The problem occurred to me on beta version of the android studio. I fixed it by upgrading it to the latest version and upgrade the gradle to the next highest version.

This problem occurred to me when I tried to run jetpack compose samples from github.

answered Jun 29 '21 at 11:22

Patrick Prakash

500
1
7
17

"Operation Succeeded" in Android Studio 4.1, with no action

11 Answers11