Android Studio Build Error Not Going Away - android-studio

I am using Android Studio v2.1.2..
This is my attempt at android development so, I am making a lot of mistakes..
However when i am correcting them, and trying to build again it's still showing the same errors;
I tried to clean the project, tried restarting Android Studio but of no luck..
Like in this pic, this apostrophe error is not going away.. i had similar errors earlier also..
They were not severe so i kept them that way..
I know this is a stupid question, but anyone could tell me how to solve this I would be grateful.
Thanks in Advance...My Problem

You have this: "Let's take a test!!!" in your values.xml file.
Update it to this: "Let\'s take a test!!!".
Always put a \ before a '(Apostrophe) in your strings.xml/values.xml/etc.
I hope I helped.

Related

Red underline res folder in android studio

I have the situation shown the following picture.
Project built successfully, but it's just annoying to see the red error warning.
How do I solve it?
Please Invalidate Caches and restart your IDE
The naming of the file also counts, remove all hyphens if there are any
Sometimes I'm seeing same picture. Gradle sync or Android studio restart helps me.

Android Studio very slow lint

I do not remember the exact version, but about from 3.2, the lint processing of Android studio has become dreadful.
ctrl + b won't work for about 5min after putting the code, and red lines which are supposed to indicate unwritten methods or wrong referencing is completely broken.
I never had such issue on the previous versions, and I don't know what to do with this. I looked through stackoverflow with the tag android-studio, but no one seems to have the same issue, or I'm selecting the wrong keyword for this.
But, all three of my colleagues are having the same issue from a certain version of Android studio.
Is this an issue with vmOption? Please help.

visual layout editor does not allow drag&drop

I'am a newby in android studio and learning a lot, but now have a problem where i cannot seem to find the answer to.
In android studio you can visualy drag&drop your screen.
I have seen it can do al lot (although you sometimes need the xml) but for me it is not working at all.
I mean i cannot drag&drop any widgets on the screen at all.
Tried changing the theme: no help (really tried a lot of them)
Tried a complete new project: same story
Tried other APK verion: same story
Tried Invalidatd caches / restart: no help
Even with a new project (EmptyActivity) it add's a android.support.v4.widget.NestedScrollView and then gives error's on that
(Failed to find style 'coordinatorLayoutStyle' in current theme).
It also gives an error on layout_height/layout_with not being there. But they are there for each widget.
Please do not missunderstand: when i execute the project i runs just fine (both on phone and emulator) but the visual builder for the screen.....:-(
Does somebody knows how to solve this.
If more info is needed please ask.
Any help is more than welcome.
There are several things that could be causing this:
Your caches could be messed up. Try going to
File > Invalidate Caches / Restart ... (I know that you already tried this, but posting for future views.)
Also, make sure that you don't have Drag-n-Drop with ALT pressed only checked in your Settings (Appearance & Behavior - Appearance).
Finally, in a default project created in Android Studio, there are two XML files created for each layout. For example, content_main.xml is embedded within activity_main.xml. Make sure that you are using content_main.xml for your design work.
In the end i fixed it by changing the SDK version in de gradle file.
still do not understand why it was wrong as studio genereded it that way but now it works so.... for me: case closed.

SSDT Fails to build Data project after clearing out my TEMP folder

After clearing out my temp folder in an effort to free up some much needed disc space, my Sql Server Data Tools (SSDT) in Visual Studio 2012, no longer builds my data project and Schema Compare is now useless ('cause it's gotta successfully build first). I get the following error message ...
Error 187 04018: The "SqlBuildTask" task failed unexpectedly.
System.IO.FileNotFoundException: Could not find file 'C:\Users\gstenstrom\AppData\Local\Temp\b3546b57-815f-43e1-92a5-831cd4844026.9.tmp'.
OK so the problem is obvious; I have clearly deleted something I needed to keep. However, I cannot replace the file as it's been deleted permanently, so what do I do to fix this issue? I have been astounded as to how little information there is about this out there so far. Any help would obviously be greatly appreciated.
Looking for a Christmas Miracle here ... quick and simple!!! :)
Thank you for your help and Happy Holidays!!
Just had the same issue. I think you figured this out as well, but just for future reference: restarting Visual Studio should fix the problem.

Unable to package app on x64: Could not copy the file "obj\x64\Release\\project_name.xr.xml

I need help resolving the following error:
Error 2 Could not copy the file "obj\x64\Release\project_name.xr.xml" because it was not found.
NOTE:
This error does not occur when I package the same solution on x86.
This only occurs on x64.
In addition, this error is now exposed ever since I downloaded VS2012 Update 2.
The error went away as a result of me fixing the list of warnings that resulted from building the solution.
For me the issue was fixed simply by removing spaces from Assembly Name parameter. This can be found in the properties of the Windows 8.1 application project.
Ok, this is a weird problem and I could not solve it till I looked at the solution from Ken.
Click here for his solution
Ken's issue and solution gave me an idea and it worked.
I had x:Class="project_name.App" in my App.xaml file and Ken said the issue was with the app name.
So I removed the .App from x:Class="project_name.App" and just had x:Class="project_name" and received the error "Invalid value for 'project_name'. Event values must be text."
Ok so I put it back in.
Well, then it worked and the error went away.
Um, I do not have any idea why it now worked as it was exactly the same text, but the process of changing it back and forth fixed it. Hope this saves someone hours of pain.
And I am using Visual Studio 2013 Update 2 that I reinstalled onto my PC yesterday since the PC had a melt down and needed a rebuild.

Resources