차근차근/안드로이드 스튜디오

No changes to deploy

예쁜꽃이피었으면 2016. 6. 23. 16:58


No changes to deploy



http://stackoverflow.com/questions/29312900/android-studio-not-deploying-changes-to-app



I've got the same problem. This thread popped up first when I've searched for it. Solved it (hoping so) by not using the Instant Run feature. Might not be the best solution but it works for now.

Just go to "File -> Settings -> Build, Execution, Deployement -> Instant Run" and just disable it. With this Android Studio builds from scratch each time but it's better than not building it right.

Mini rant: Almost each version of Android Studio comes with an annoying bug. They're about to release the version 2 but its beta is still buggy. I hope they stabilize the IDE in the near future.

shareimprove this answer
2 
I'm using Android Studio 2.1 and I still have the same issue. The only solution was to disabled the instant run :( – radu_paun May 10 at 8:04

GUI Picture

I had the same Problem, using Android Studio 2.0.0, solved it by rebuilding my Project.

Build > Rebuild Project

shareimprove this answer

This was a real stumper until I realized that my changes must not be propagated to all relevant files ...

If you're having trouble with layouts, as I was, you may find that you need to update the layout in theres > layout-v17 folder. I had made changes via the Design View in the layout folder and those changes seemed to be propagated automatically to layout-v17, initially. However, later changes WEREN'T.

Check your res > layout-v17 folder and see if the .xml files in that folder reflect the changes you are seeing in your res > layout folder. You will probably find that they don't. Fix this and re-deploy. Like me, you should see the new code mods.

Hope this helps.

shareimprove this answer

Same problem started occurring after I have upgraded the buildVersion from 23. Tried removing AVDs and recreating, Synching up with Gradle Files. Nothing helped. Complete reinstallation of Andriod Studio has fixed the problem. This may not be the solution but this only worked for me.

shareimprove this answer

Also me solved it by not using the Instant Run feature. Might not be the best solution but it works for now. I'm using Android Studio 2.0 beta 2...

shareimprove this answer
1 
please elaborate more on your answers so other users can benefit...add step by step, etc... – Juan Pablo Boero Alvarez Feb 10 at 20:19
   
Someone else has already posted this as an answer. Instead of re-posting, consider upvoting the existing answer once you have enough rep. – OhBeWise Feb 10 at 20:21

For now I solved the issue by closing the app and run again. It worked like a charm. Not sure yet if it is a coincidence, but i guess it worths give it a try.

I really wonder if it works some other people too. Lets give it a try and let me know.

shareimprove this answer


반응형