I'm new to android studio and to android development in general. My application was building fine but now the Gradle fails to build with the following error message:
Gradle tasks[:app:assembleDebug]
null value in entry:aaptFriendlyManifestOutputDirectory=null
I haven't found any other threads encountering this issue and don't really know where to start to resolve it.
Deleting the .Gradle file resolved this issue for me!
Related
I run a kotlin project successfully on my desktop, but when I import the same project on my laptop and when I rebuild the project, it's throwing "org.jetbrains.kotlin.util.KotlinFrontEndException: Exception while analyzing expression".
As suggested in net, I tried with clean build, invalidate cache and restart. I deleted the cache folders and logs but no results.
I have tried Googling, but found no answer for this particular problem.
Details:
Current kotlin plugin version: 1.3.61-release-Studio3.5-1, latest version of plugin is installed, using Android Studio 3.5.2
Any help is apreciated!
I was facing a similar error, updating Kotlin Plugin and restarting Android Studio fixed the issue for me
This seems to be a sync issue. To solve this, I performed these two steps in succession and then re-ran the project:
Deleted the entire build folder
Build > Clean-Project
In my case I was missing some jar files that were required for the app to build. So if you encounter this, check if you have all required dependencies on your classpath.
In my case it was broken xml layout file (the expection message did not indicate the file).
Got following error after updating Android Studio from 171.xxxxx to latest 173.xxxxx. I am not able to build any project due to this. Tried various ways but unable to find the solution. I really appreciate your help!
Add following line in gradle.properties and build and run
android.enableAapt2=true
I have no Idea what is happening, last time when I finished my app I build its release apk and all was working just fine as expected but now today when I tried to make that pproject again and to make another apk I am getting the following error.
Error:Execution failed for task ':app:mergeDebugResources'.
Crunching Cruncher common_signin_btn_icon_pressed_light.9.png failed, see logs
I have no idea how to resolve it I have serached and found restarting Android studio and clean the project would remove it , doing this many times has no effect on this error. I have even restarted my machine but the condition of error in same.
In the logs I have seen that this png file is from the library I added , so just for testing I removed that library and tried to build then it started to give me same error with different png file name in other library. So how to fix this issue ?
My Questions are :
How can this issue be Solved ?
Have some one faced this problem too ?
Is this problem has been reported to google ?
Why in android we do not have any stable platform for development as IOS have ?
Try to remove "builds" folders and do rebuild. But soon, the whole thing in a long file name. Read this answer. By the way, you looked logs? Maybe this is not the PNG? You have not sent the log and did not specify the version Gradle.
Believe me, iOS developers have own problems.
I imported a project from other's workspace running succusfully there in Api 21 .There is no error in code after importing it in mine but as i run the project in eclipse after updating it to android SDK 21 it shows trouble writing output: already prepared .There may be some problem in configuration .console please help me to fix this problem.
This is not about configuration, it´s about old files...
Clean Project
Refresh Project
Build Project.
Run
I am using Android Studio 0.5.2 and everything was ok 2 hours ago. After reopening the project now it gives the following error.
Gradle 'ProjectName' project refresh failed: Failed get query package
name for debug
How can i solve this error?
I got this error and found out it was because I had errors in AndroidManifest.xml. Some errant text ended up in the file and created numerous errors. I reverted to a previous known good version and Gradle refreshed without issue.
I have had problems like this a few times. Usually if you close it and reopen it the problems go away.