Flutter : Several variant outputs are configured to use the same file name - android

I am just trying to run the first app and this is what happens:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:packageDebug'.
> Several variant outputs are configured to use the same file name "resources-debug.ap_", filters : MAIN:MAIN

Please try flutter clean and rebuild.

I got the same error while trying to integrate FCM into my application.. The problem is in the older build file.. i.e as we are editing our Manifest file we need to rebuild the project so..
flutter clean
flutter run
Make sure to do gradle sync if the problem persist..
It solved the problem for me..

Close and reopen IDE
flutter clean
flutter run

just log out from current windows session and then do flutter clean and after run your project. that will solve the problem.

If flutter clean doesn't work, then delete the Android folder, then run flutter clean and run the app... Make sure you have an android emulator or device connected as your run device, this will bring a prompt asking you to enable android for your project then just click yes.
You can also uninstall the app from your emulator or android device before you run it again, but make sure its uninstalled on all profiles of your device.

this error also appear when you mistakly disable the app and try to debug same app again.So go to applications and enable it again to resolve the issue.Thanks

remove pubspec.lock
flutter clean
flutter run

Related

Android Studio Fails with: "File was deleted, but previous version not found in cache"

I had a project on Android Studio which was working. But after I ran
git pull and then git reset --hard and tried to run it again, build failed with the message:
File 'com.android.builder.files.ZipCentralDirectory#412e039a' was deleted, but previous version not found in cache
Build -> Clean Project fixed my problem.
Go to Task Manager
Search for any instances of OpenJDK or java in task manager click and End Task
Run flutter clean in IDE
The Reason was Flutter Clean cant delete the build while the Application is still running in the Background process, u have to close it and run.
I also faced the same issue. it occurs when you run> flutter clean command that actually did't clean all the files inside build directory of your project, and causes the issue.
So the simple solution is, delete your build directory manually. If it alerts "File in Use" dialogue then simple do the following steps
open the run command with shortcut Window+R
type resmon.exe it will open the resource monitor
click on "CPU" tab
click on "Associated handles" and type build in search bar
right click on java.exe and end process
restart your IDEA and run your project the problem is solved
An alternative way to fix this issue is to run flutter clean.
You mentioned you are using android studio, go to your terminal inside android studio and then run the above mentioned command.
After the above command was executed then run your app again.
This simple solution worked for me !
Using Android Studio 3.6.2 for a Flutter project there is no 'Build -> Clean' unless you 'Open Android module in Android studio'. Then there is a 'Build -> Clean Project'.
An alternative as mentioned above is to open the terminal in the project where you may Debug your application and run 'flutter clean'.
For me the latter is better since I typically only open the Flutter android module when I want to build a release of my app.
Open Android module in Android studio
run success
execute ‘Build -> Clean’
close Android module in Android studio
run flutter project again

Installation failed with message Failed to commit install session

Getting an error message while trying to run an apk through android studio 3.4 canary 1.
Gradle plugin version com.android.tools.build:gradle:3.4.0-alpha01
Installation failed with message Failed to commit install session 526049657 with command cmd package install-commit 526049657.. It is possible that this issue is resolved by uninstalling an existing version of the apk if it is present, and then re-installing.
I have tried uninstalling the apk, restarting android studio and the device and invalidating caches and rebuilding but nothing seems to work.
I disabled "Instant Run" in settings, and it works for me.(Android Studio 3.4 canary)
Then you can see the adb command executed in the terminal is "adb push", while it is "adb install-multiple" before that is disabled.
On Android studio go to build menu :
Build menu
Then:
First Clean
Rebuild
run it again
*******It works well **********
build->clean project
rebuild project
Delete as shown below
Disable "Instant Run".
File->Setting->Build, Execution, Deployment->Instant Run-> unCheck (Enable Instant Run to hot swap code/resource changes on deploy)
and Run your Project and after that go and Enable Instant Run to use the advantages of Instant Run
If you have a version of the APK installed on a device/emulator and you create a new version of the APK that compiles against an SDK above the device/emulator sdk, you get this error vs. the original "yo, you are targeting 28 and this device has 26... come one, you need a 28 device/emulator".
You have to actually turn off instant run to see the right error.
Why would you do this? Good question! I mixed up my Q vs P devices and wasted an hour trying to figure out what was going on. :P
Most easy solution is, wipe data of your emulator and run project again.
I had fixed this problem by getting rid of the meta data section in my manifest. I have no clue how it was added to the manifest to begin with (I'm a noob), but once I removed it from the manifest, the app loaded right up.
<Activity
...
/>
remove the meta data line within the manifest and it should work.
This is what worked for me
Build > Clean Project
File > Invalidate Caches & Restart
Just checked In AndroidMainfest file is not complaining any issue.
I have updated targetSDK version 33 and it required "android:export" flag in activity section

Run button isn't compiling project in Android Studio 3.1 [duplicate]

When I try to install an app, there are two possibilities:
Install existing APK from build folder when I run the app
Install APK after performing clean build
For existing APK in the build folder, the app just works fine. But when I clean the project using Build -> Clean Project, and then try to run the app (i.e. install the app to my emulator or physical device), it shows me error:
The APK file /Users/MyApplicationName/app/build/outputs/apk/app-debug.apk does not exist on disk.
NOTE: This behaviour happens only when I clean the project and not when I have already have a pre-built app APK in my build folder
I've referred to: The APK file does not exist on disk but my point is, when we usually run the app after cleaning the project, we never need to make a build of it, if the APK is not existing in the build folder, it automatically generates and installs the latest one.
Things I've tried:
Running the app when APK file exists in the build folder (works perfectly fine)
Running the Clean Project -> Running the app (expected is the project would be built and the app would get installed but it shows the above mentioned error!)
Same process of cleaning and running the app after doing Invalidate Caches/Restart
I have solution for your issue.
Also confirmed by Android Studio on Twitter : https://twitter.com/androidstudio/status/981914632892960768
Edit your app configuration as below.
Here you can see your app configuration as below.
Here is missing Gradle-aware make attribute in before launch configuration. You can see here.
Please add this Gradle-aware Make attribute through this way. Click on + icon and select Gradle-aware Make as seen in this screen.
You can add this without writing any task just press OK button and task will be added and now it should look like this. Now apply changes and run your application.
It will solve this old apk installing issue on clean build in new Android Studio 3.1 issue.
Note : This issue is resolved in new Android Studio 3.1.1 Stable release.
The APK file
/Users/MyApplicationName/app/build/outputs/apk/app-debug.apk does not
exist on disk.
May be bug. You should change Settings.
You should open the Run/Debug Configurations dialog & select Run > Edit Configurations
Make sure, Gradle-aware Make is Added in TaskList or not. If not then click + & select from the options.
Note
If you receive
Shutdown finished in 0ms Error while generating dependencies split APK
com.android.ide.common.process.ProcessException: Failed to execute
aapt at
com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:809)
at
com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:797)
at
com.android.build.gradle.internal.transforms.InstantRunSplitApkBuilder.generateSplitApkResourcesAp(InstantRunSplitApkBuilder.java:373)
You should Un-Check INSTANT RUN.
File-- Settings-- Build, Execution, Deployment -- Instant Run and
uncheck Enable Instant Run.
clean your project and run again
If it's not work then
Step 1 Close your project.
Step 2 Go to your project folder and delete all build folder.
Step 3 run your project.
This issue has been fixed with Android studio 3.1.1 (April 2018) release.
Update your android studio to 3.1.1.
Here is there explanation regrading the issue details, cause and solution:
In some cases, when a project created in Android Studio 3.0 was opened for the first time in Android Studio 3.1, the Gradle-aware Make task was removed from the Before launch area in Run/Debug Configurations. The result was that projects did not build when the Run or Debug button was clicked, which in turn caused failures such as deployment of incorrect APKs and crashes when using Instant Run.
To solve this problem, Android Studio 3.1.1 adds the Gradle-aware Make task to the run configuration for projects that are missing this entry. This modification occurs after the first Gradle sync when the project is loaded.
Official release notes: https://developer.android.com/studio/releases/index.html#3-1-0
For all people seing this and having the issue on Android Studio +4.0.0:
Run -> Edit configurations... -> disable check box (Allow parallel run)
It may slow your build a little but it better than running the app more than one time.

Android Studio 3.1 is not compiling/building the app, runs instantly [duplicate]

When I try to install an app, there are two possibilities:
Install existing APK from build folder when I run the app
Install APK after performing clean build
For existing APK in the build folder, the app just works fine. But when I clean the project using Build -> Clean Project, and then try to run the app (i.e. install the app to my emulator or physical device), it shows me error:
The APK file /Users/MyApplicationName/app/build/outputs/apk/app-debug.apk does not exist on disk.
NOTE: This behaviour happens only when I clean the project and not when I have already have a pre-built app APK in my build folder
I've referred to: The APK file does not exist on disk but my point is, when we usually run the app after cleaning the project, we never need to make a build of it, if the APK is not existing in the build folder, it automatically generates and installs the latest one.
Things I've tried:
Running the app when APK file exists in the build folder (works perfectly fine)
Running the Clean Project -> Running the app (expected is the project would be built and the app would get installed but it shows the above mentioned error!)
Same process of cleaning and running the app after doing Invalidate Caches/Restart
I have solution for your issue.
Also confirmed by Android Studio on Twitter : https://twitter.com/androidstudio/status/981914632892960768
Edit your app configuration as below.
Here you can see your app configuration as below.
Here is missing Gradle-aware make attribute in before launch configuration. You can see here.
Please add this Gradle-aware Make attribute through this way. Click on + icon and select Gradle-aware Make as seen in this screen.
You can add this without writing any task just press OK button and task will be added and now it should look like this. Now apply changes and run your application.
It will solve this old apk installing issue on clean build in new Android Studio 3.1 issue.
Note : This issue is resolved in new Android Studio 3.1.1 Stable release.
The APK file
/Users/MyApplicationName/app/build/outputs/apk/app-debug.apk does not
exist on disk.
May be bug. You should change Settings.
You should open the Run/Debug Configurations dialog & select Run > Edit Configurations
Make sure, Gradle-aware Make is Added in TaskList or not. If not then click + & select from the options.
Note
If you receive
Shutdown finished in 0ms Error while generating dependencies split APK
com.android.ide.common.process.ProcessException: Failed to execute
aapt at
com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:809)
at
com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:797)
at
com.android.build.gradle.internal.transforms.InstantRunSplitApkBuilder.generateSplitApkResourcesAp(InstantRunSplitApkBuilder.java:373)
You should Un-Check INSTANT RUN.
File-- Settings-- Build, Execution, Deployment -- Instant Run and
uncheck Enable Instant Run.
clean your project and run again
If it's not work then
Step 1 Close your project.
Step 2 Go to your project folder and delete all build folder.
Step 3 run your project.
This issue has been fixed with Android studio 3.1.1 (April 2018) release.
Update your android studio to 3.1.1.
Here is there explanation regrading the issue details, cause and solution:
In some cases, when a project created in Android Studio 3.0 was opened for the first time in Android Studio 3.1, the Gradle-aware Make task was removed from the Before launch area in Run/Debug Configurations. The result was that projects did not build when the Run or Debug button was clicked, which in turn caused failures such as deployment of incorrect APKs and crashes when using Instant Run.
To solve this problem, Android Studio 3.1.1 adds the Gradle-aware Make task to the run configuration for projects that are missing this entry. This modification occurs after the first Gradle sync when the project is loaded.
Official release notes: https://developer.android.com/studio/releases/index.html#3-1-0
For all people seing this and having the issue on Android Studio +4.0.0:
Run -> Edit configurations... -> disable check box (Allow parallel run)
It may slow your build a little but it better than running the app more than one time.

App installation failed when transfered code

So i started my project on Mac OS and than with USB i transfered to MacOS, using same version of Android studio, but on Mac it doesn't want to run i tried to delte gradle and idea folders build a gradle and all but no success. The error i get is Application Installation Failed:
Installation failed with message Invalid File: /Users/myuser/Code/App/E:\Android\apps\build\intermediates\split-apk\debug\slices\slice_2.apk
Do you want to uninstall this existing application?
So as it looks like its picking up my Windows things from somewhere any idea how i can fix this?
Just Clean & Rebuild the project.
So i just run: ./gradlew clean and disabled instant run and its working now.

Categories

Resources