I am having some trouble with Android Studio and flutter. Every time I make a change in the pubspec.yaml file of my flutter app and save the change, then run my app in my phone, my computer gets stuck while building the app.
Its stucks while running gradle -> Running Gradle task 'assembleDebug'...
I am forced to restart my laptop and then run AS again. The app will now run in my phone but anytime I open pubspec.yaml and make some dependency changes, then my computer will get stuck again and I have to restart again.
Below are some details that might be helpful.
I had tried the same with Ubuntu 18 and I was still getting a similar challenge.
How do I resolve this?
The solution was to change the Operating System and reinstall it again afresh. I did not manage to get a simpler solution
I'm working on 2 applications.
One is a bootloader for another which is a main app.
They both have technically the same gradle settings (except package names).
The problem I have is that Android studio always rebuilds entire application for main, but for bootloader app, it just makes changes.
For example:
When I press run on main application, these tasks gets executed (these tasks gets executed even if I don't edit anything):
Executing tasks: [:app:clean, :app:generateMesiDebugDebugSources, :app:generateMesiDebugDebugAndroidTestSources, :app:prepareMesiDebugDebugUnitTestDependencies, :app:mockableAndroidJar, :app:assembleDebugDebug]
While on bootloader app, these tasks gets executed:
Executing tasks: [:app:incrementalDebugSupportDex]
I'm sure I had changed something in my first app in settings but I can't figure out why. Each rebuild on main app takes about 2.5 min while executing small task on bootloader app takes about 2 seconds only, even if I make small changes (view changes, small activity changes).
I'm using Android Studio 2.1 (updated today), but these happens to me about 2-3 days ago.
My gradle version is 2.1.
Hope someone knows how to force Android studio to only compile and build changes in code, not entire app.
Thanks for answers.
Edit: Instant run command is enabled.
I think "Instant Run" setting is not enabled in your first application.
Mac
Go to Android Studio->Preferences->Build, Execution, Deployment->Instant Run->Select the Enable Instant Run check box
Windows Use the settings dialog and do the same procedure mentioned above
Exactly my problem, if I have small change in app about display UI (modify activity code or resource layout), Android studio build very fast and then run my app in emulator without kill "previous version" process (running in emulator), sometime it's run and display correct, but sometime it doesn't run correct what I want, I must kill process manual and rebuild project, it takes a lot of time, and makes me confused because I don't know where go wrong,
I thought this is my bug.
It happen recently when I update Android studio, I think this feature is very powerful and helpful, application mustn't rerun from the beginning whenever build new version.
But how to enabled/disabled "fast build", sometime I want Android studio build my project normally.
You have 2 solution:
1)You can also disable Instant Run from Settings > Build,Execution,Deployment > Instant Run - and disable it
2)Clean Project when studio doesn't build properly
Press the stop button before running the app and then run the app so dialog will be displayed to choose the emulator.
I recently switched from Eclipse to Android Studio because I read that it is now the official IDE for Android application development. I downloaded and installed the latest version (1.0.2) for Windows. When using the program for the first time, I decided to create a test application to see if the program was working correctly. Unfortunately, it was not. Once I clicked the finish button to complete the New Project Wizard, A loading bar showed up that said Gradle: Build. This is where the program gets stuck. There is no error message and it appears that the program is running fine, however the build never actually completes. I am never given my MainActivity.Java class, or my activitymain.xml document. If I click the cancel button, the program freezes and I have to use the TaskManager to kill the program. If I re-enter the program and choose to open an existing project, my project will be there. However, upon trying to open the project, I am greeted with the same Gradle: Build loading bar.. I have been searching for an answer for the last 3 days and nothing has worked. Any help is greatly appreciated!
Things I have tried:
Simply letting the program sit for a while to see if it was actually downloading something and was just really slow. I let it sit for 45+ minutes before killing the program.
Uninstalling and re-installing Android Studio
Restarting my computer
Turning off my firewall (Kaspersky)
Running the program as an administrator
Connecting to a different network
Disconnecting my computer from any networks (to force the program to build in offline mode)
Manually downloading Gradle from the link that Android Studio attempts to use when it gets stuck and telling the program to use that file instead of downloading another one.
(I went to this link https://services.gradle.org/distributions/gradle-2.2.1-all.zip, downloaded the file, unzipped it, went to Gradle settings in Android Studio, checked the Offline work checkbox, and finally set the service directory path to my unzipped Gradle folder.)
Hopefully I have given enough information and made it clear what my problem is. If not please tell me what else I need to explain so I can get this issue resolved. Thanks!
Please note I am working on a 64 bit machine running Windows 8. Also, I use studio64.exe
to run the program.
From the discussion we had in the comments, it does not look like you have your gradle on your windows path.
Please change the below to point to your gradle install:
set GRADLE_HOME=C:\<installation location>\gradle-1.11
set PATH=%PATH%;%GRADLE_HOME%\bin
After this, verify that in the terminal running the following works:
gradle tasks
once you get this working, you will want to run the following in your project:
gradle wrapper
This will produce a .bat file which you can then use to run gradle through the wrapper, letting you support multiple native gradle installations.
I'm trying to update Android Studio from 0.5.1 to 0.5.2 on two separate Windows machines, one with Windows 7 Pro 64-bit and one with Windows 7 Enterprise 64-bit.
I get the normal update prompt:
...and if I choose "Update and Restart", the patch downloads and the IDE exits, but then I get the following dialog:
I can't change any of the "Solution" column entries. If I click "Proceed", I get the following message as shown below (image and text, so its copy/paste/search-friendly):
Temp. directory: C:\Users\Sean\AppData\Local\Temp\
java.io.FileNotFoundException: C:\Program Files (x86)\Android\android-studio\lib\jsch.agentproxy.usocket-nc.jar (Access is denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
at com.intellij.updater.Utils.copyStreamToFile(Utils.java:135)
at com.intellij.updater.CreateAction.doApply(CreateAction.java:52)
at com.intellij.updater.PatchAction.apply(PatchAction.java:140)
at com.intellij.updater.Patch$3.forEach(Patch.java:198)
at com.intellij.updater.Patch.forEach(Patch.java:248)
at com.intellij.updater.Patch.apply(Patch.java:194)
at com.intellij.updater.PatchFileCreator.apply(PatchFileCreator.java:86)
at com.intellij.updater.PatchFileCreator.apply(PatchFileCreator.java:77)
at com.intellij.updater.Runner.doInstallImpl(Runner.java:307)
at com.intellij.updater.Runner.doInstall(Runner.java:268)
at com.intellij.updater.Runner.access$000(Runner.java:18)
at com.intellij.updater.Runner$2.execute(Runner.java:258)
at com.intellij.updater.SwingUpdaterUI$7.run(SwingUpdaterUI.java:230)
at java.lang.Thread.run(Thread.java:744)
When I click "Exit", Android Studio re-opens, and tells me that the update is still available.
I've updated Android Studio previously using this same method on both machines without a problem.
Since I believe this is some kind of bug with Android Studio specific to newer releases, I've opened Issue 67794 on the AOSP issue tracker.
EDIT
I was able to update from 0.5.2 to 0.5.3 today on both machines without encountering this issue. I was shown the Windows security prompt for the JetBrains installer as in previous successful updates, and update completed successfully without me having to start Android Studio with elevated permissions. So, seems the problem was something specific to 0.5.1 or 0.5.2 patches.
EDIT
I encountered a similar error when trying to update from Android Studio 0.6.0 to 0.6.1:
Temp. directory: C:\Users\barbeau\AppData\Local\Temp\
+----------------
A file operation failed.
This might be due to a file being locked by another
application. Please try closing any application
that uses the files being updated then press 'Retry'.
+----------------
com.intellij.updater.RetryException: Cannot delete file C:\Program Files (x86)\Android\android-studio1\lib\openapi.jar
at com.intellij.updater.BaseUpdateAction.replaceUpdated(BaseUpdateAction.java:40)
at com.intellij.updater.UpdateZipAction.doApply(UpdateZipAction.java:199)
at com.intellij.updater.PatchAction.apply(PatchAction.java:140)
at com.intellij.updater.Patch$3.forEach(Patch.java:198)
at com.intellij.updater.Patch.forEach(Patch.java:248)
at com.intellij.updater.Patch.apply(Patch.java:194)
at com.intellij.updater.PatchFileCreator.apply(PatchFileCreator.java:86)
at com.intellij.updater.PatchFileCreator.apply(PatchFileCreator.java:77)
at com.intellij.updater.Runner.doInstallImpl(Runner.java:307)
at com.intellij.updater.Runner.doInstall(Runner.java:268)
at com.intellij.updater.Runner.access$000(Runner.java:18)
at com.intellij.updater.Runner$2.execute(Runner.java:258)
at com.intellij.updater.SwingUpdaterUI$7.run(SwingUpdaterUI.java:230)
at java.lang.Thread.run(Thread.java:745)
This seems to happen if you try to run the update while the Gradle build process is still running (e.g., right after you start up Android Studio).
A workaround:
Close Android Studio.
Right-click "Android Studio" icon and select "Run as administrator".
Go to "Help->Check for Update...", and go through the normal update process
I realized after a few failed update attempts from 0.5.1 to 0.5.2 that I was no longer getting the Windows security prompt to allow the JetBrains IntellJ installer to proceed, as I had seen in previous successful updates. I'm not sure what changed from previous updates, but apparently the update process was unsuccessfully trying to access files without proper permissions. Elevating Android Studio to admin through the above process fixed the issue.
As noted in the question above, this issue no longer seems to occur with the update from 0.5.2 to 0.5.3.
EDIT
To fix the next error I encountered with the Android 0.6.0 to Android 0.6.1 update, I shut down Studio and then restarted it, and let it sit overnight (more by coincidence than design). When I returned to the machine in the morning and ran the update, it succeeded. So, it seems there is some kind of long running process that blocks the update under certain conditions (likely immediately after startup - possibly the Gradle build process?). #Daniel Wilson's answer below should also work for this scenario.
This happened with me updating from 0.6.0 to 0.6.1. I had attempted to open AS in admin mode with every other application closed but the update still failed for me. I also tried deleting the Temp folder.
Eventually I noticed in the task manager when everything was closed I still had a sizeable java.exe still running in the background for some reason.
What I did was open AS in admin mode, run the update and let it fail, claiming a file is locked / access is denied or something similar. Open the task manager and I noticed 2 java.exe processes running. For me the smaller one (about 200k) was the AS updater utility itself. But if I killed the larger one (about 600k), and hit retry, the update went through without issue.
Don't re-install as an Administrator!
Whilst running in Admin mode might make the update work, it may also affect the permissions that are set on any files that are added and/or updated, such that future operations in Android studio that use such files will need elevated (Admin) access to work properly.
Doing this will result in many operations not working unless Android Studio has been run in elevated mode.
Instead, deal with the file lock, then try again:
Try killing all instances of java.exe (in Task Manager or Process Explorer), then re-attempt the update, but not running as Administrator.
Every time I've used Process Explorer (on Windows) to check which application has a lock on one of the files that's blocked an Android Studio update, it's always been Java.
What worked for me (on Windows):
Download Process Explorer, and kill all instances of java.exe: in Process Explorer, sort by the Process column and find java.exe instances, press Del on the highlighted row. (On a side note, the file that's blocking the update, for example jsch.agentproxy.usocket-nc.jar, can be checked by pressing Ctl+F, and then entering the file name)
If the update process doesn't automatically resume, kill it by dragging the target icon to the update process' window - this locates it in Process Explorer's Process window - and then press Del to delete the process
Re-run Android Studio (from start menu), and re-initiate update process.
You might also try to give your user permission to the folder.
Right click the "android-studio" folder and select "Properties"
Change to "Security" tab
Click the "Edit" Button
Select the group/user from the "Group or user names" list
You can select/add your username to this list -or-
Select the group "Users" (or the group where your user is)
Select the "Full control" checkbox
Click "Apply" and wait
You're done.
Disable antivirus and try update again.... Worked for me.
I had a Java process running in the background on my Windows machine that wasn't showing up in my Task Manager. This will make sure Java gets killed:
taskkill /F /IM java.exe
I've stuck at the same issue, but I solved it by running this script in elevated console:
Program Files\Android\android-studio\bin\update_studio.bat
I solved a similar problem while updating Android Studio by just closing all other running applications, such as Firefox and restarted the update process.
It seems that a file is just by another program and it cannot be accessed by Android Studio.
Another way to solve this problem is to delete all files in the corresponding folder, such as: User/AppData/Local/Temp
I had the same problem - update from 0.6.0 to 0.6.1
After pressed button "Update", Android studio restarted and started to update. After this I got "Error message". I pressed "Retry" button - it was unsuccessful. Then I waited about 2 minutes (in my studio after start Gradle is working) and pressed again "Retry" - Done! :)
Everything was updated. So in my case the reason of problem was Gradle that works after start of Android studio.
I used LockHunter to see what was locking the files. Result: Adb had locked some of them (I was testing the application by wifi in a mobile phone). I killed adb server, restart the Android Studio and I was able to update it.
Good luck for others!
I had this same issue updating from 2.2 to 2.2.1.
My solution was restarting Windows