Recently the Android Studio 3.5 updates and now Android Studio 3.6, the editor window does not wrap the text so some lines are long and go off the right of the screen. I don't want to scroll left and right all the time, so would like the text to autowrap. I've read many posts on the issue but nothings has solved it.
I've tried going to
Preferences -> Editor -> General and enabling soft wraps there, but that hasn't helped.
I tried adding *.java to the soft wraps files but that didn't help.
The only thing that works is selecting View -> Active Editor - Soft Wrap. That formats the current editing window with auto wrap, but each time I open a new java file auto wrap is not enabled I would need to enable it again. This is so frustrating and was never an issue before Android Studio 3.5. Any help would be appreciated.
I had the same problem, and my solution should work for you. The delimiter in the soft-wrap file list is a semicolon, not a comma: change your comma to a semicolon.
I installed android studio.. it was working fine. Now all the sudden, none of the auto complete features are working.. I can type anything anywhere no variable checking, no help with functions or checking anything. I can still compile the project and I get errors when that happens.
Can anyone please help me out with this issue.
#1 From Build menu (of your Android Studio), click Rebuild Project option.
#2 Then once rebuild completes, go to File > Invalidate Caches / Restart... and Click on Invalidate an Restart button.
This really works for me.
Source: https://code.google.com/p/android/issues/detail?id=61844#c4
#1 Rebuild is required, because Android-Studio does simply rely solely on Gradle's build-result (without static-analysis support, at least at time of writing, 2022).
#2 Clearing cache is required, because the previous build-result (before above rebuild) may be indexed, which makes Android Studio ignore latest Gradle build-result
(this is a very good speed optimization, but a very bad Developer-experience as well).
There can sometimes be other reasons too, which is why there are many other answers posted here.
You can also check if Power Save Mode on File menu is disabled.
Close Android Studio
Go to C:\Users\UserName\.android and rename the folder:
build-cache to build-cache_old
Go to C:\Users\UserName\.AndroidStudio3.x\system
OR (for Android studio 4 and Higher) go to C:\Users\UserName\AppData\Local\Google\AndroidStudio4.x
and rename these folders:
caches to caches_old
compiler to compiler_old
compile-server to compile-server_old
conversion to conversion_old
external_build_system to external_build_system_old
frameworks to frameworks_old
gradle to gradle_old
resource_folder_cache to resource_folder_cache_old
Open Android Studio and open your project again.
Originally use:
compileSdkVersion 32
targetSdkVersion 32
And an update to 33 appeared, I updated it and the suggestions in the XML no longer appeared, I went back to 32 and now the suggestions appeared.
Close Android Studio
Go to c_users_path_on_windows/.AndroidStudio3.5/system/
Delete the cache folder
Start Android Studio
This works for me.
Most of the times i have seen that the problem is that Power Save Mode is enabled, to disable go to Current inspection profile (lower right corner in Android Studio).
I have not run into this problem personally, but try checking the following settings (File -> Settings or Alt+F7):
Project Settings [name]
Inspections - ensure that Android and Android Lint is checked, or alternately just set it back to default using the dropdown box at the top.
IDE Settings
Editor -> Code Completion - ensure the Autopopup code completion is checked (and check the rest of the settings based on your preference.
Uncheck "Power Save Mode" in "File" tab
If nothing works (like happened with me ) go to your user profile in windows at %userprofile% . You will find folders there (hidden) named with the version of the android studio you are using and prefixed with a dot.
like .AndroidStudio3.1. Just delete that .
Solution: Try disabling "File -> Power Save Mode" in Android Studio (Beta) 0.8.14 - Mac OS X
On windows, the option can be at some other place.
I had the same problem then I recalled that while exploring the new android studio, I switched on the "File -> Power Save Mode" to see what it does?
I disabled the power save mode and all those intelligent features were back.
It turned out that in Power Save Mode, Android Studio switches off the modules responsible for features like Smart Code Completion and Code Analysis.
I had a similar problem where none of the other solutions worked.
Closing Android Studio and then deleting the .idea and build folders resolved the issue.
Disable Power Save Mode and Invalidate Cache and Restart.
For Artic Fox 2020|3.1 Version: Auto Complete Suggestion Problem.
Please Follow the Following Steps:
Close Android Studio
Locate caches folder in C:\Users{username}\AppData\Local\Google\AndroidStudio2020.3
and Delete it.
Open Android Studio Again.
Check your Android studio version and Target that version folder at below location
C:\Users{username}\AppData\Local\Google
Note : AppData folder is Hidden in Windows
This Solution also works if android studio mess up with xml files and java code. Don't! modify your code otherwise IDE won't able to change it to default. If you see such messy code just follow above steps and your code will be fine again.
It's Working
Disable Power Save Mode
Untick Power Save Mode Option ::
File -> Power Save Mode
There is a power saver mode in android studio if accidentally you click on that it will disable code analysis which will reduce the battery consumption and performance will also increase but it will not detect any errors and do auto complete operations.
To disable power saver mode
- Go to File Menu of Studio
- Uncheck The Power Saver Mode
In your IDE code analysis will be shown using an eye symbol at the right corner of your android studio.
If Green means it is enabled and there is no error in your code.
If Red Means It is enabled but there are few errors in your code.
If It is white or blur then code analysis is disabled
Just remove all the folders named AndroidStudioPreview
On Windows:
Go to your User Folder - on Windows 7/8 this would be:
[SYSDRIVE]:\Users[your username] (ex. C:\Users\JohnDoe)
In this folder there should be a folder called .AndroidStudioPreview
On Mac OS X
Remove these files:
~/Library/Application Support/AndroidStudioPreview
~/Library/Caches/AndroidStudioPreview
~/Library/Logs/AndroidStudioPreview
~/Library/Preferences/AndroidStudioPreview
There can be several things which cause this.
Make sure you've write the correct version in targetSdkVersion and compileSdkVersion.
Make sure targetSdkVersion and compileSdkVersion are same.
Other solutions can be:
Invalidate caches & restart Android Studio from File → Invalidate Caches / Restarts...
Clean your project from Build → Clean Project
Rebuild project from Build → Rebuild Project
Make project from Build → Make Project [this process may take some time]
Be sure to check for IDE errors by clicking the button at the bottom right of android studio.
In my case, there was a bad plugin, and the IDE Fatal Errors window prompted me to uninstall the plugin. (I wish I'd known about this feature before spending half a day invalidating caches, deleting folders, and reinstalling android studio with no luck.)
It worked for me.
From menu select:
File -> Power Save Mode
and make sure it's disabled
Go TO Left Side Top File Option
Then Click To Power Save Mode
Disable Power Save Mode That Fix This Issue
In my case, when I switch keyboard language to English, the auto complete works again.
if the autocomplete isn't working for you in Android Studio, just press File and uncheck the Power save mode, it should work fine after that.
if power save mode is already unchecked then first check then uncheck them.
If you have a library project included, make sure the library has the dependencies in build.gradle listed using the api configuration, not the implementation configuration.
Also make sure that the project that includes the library has all the dependencies listed (using the implementation configuration is fine here).
'The file size (2561270 bytes) exceeds configured limit (2560000 bytes). Code insight features are not available.'
Had this issue for days with none of these proposed solutions working before eventually getting this message in yellow under the tabs after adding a line of code. Removing the line of code eliminated the message but not the issue. There appears to be a code size window where you lose insight features but don't get this message, at least for me. Once you go over a certain point the message finally pops up. The suggested solution in a different thread for this issue was to edit 'Help/Edit Custom Properties' to increase the configured limit, but just opening this brought up a dialogue asking if I wanted to create an 'idea.properties' folder so I decided not to risk that approach over eventually cutting the file size.
If sometimes this problem can occur if you misspelled a file extension or make a file without adding an extension.
Check you have added the file extension correctly.
I think that answer may help you.
I'm using mac and suddenly the code completion (^space) not working. There are no errors. Turned out the android studio's shortcut was conflicted with system's shortcut. I don't know why it suddenly happen because it was fine before, maybe there was an update on my Mac.
See below setting for the conflicting shortcut
In my case, C:\Users\UserName\AppData\Local\Google\AndroidStudio2020.3\ just delete caches folder and restart android studio. after deleting this caches folder my problem was solved :)
I encounter with this problem while adding a kotlin library into my project on mac. Changing macbook language to english solved this problem. I also had some weird problems with auto-generated databinding codes, those are also solved.
Try Invalidate caches/Restart from File in Menu Bar from android studio.
Close Android Studio
Go to
C:\Users\YOUR_USERNAME\.android
and rename the following folder to:
build-cache to build-cache_old
then Go to (Android studio lower then version 4)
C:\Users\UserName.AndroidStudio3.x\system
OR (Android studio 4 and Higher) Go to
C:\Users\UserName\AppData\Local\Google\AndroidStudio4.x
or
C:\Users\UserName\AppData\Local\Google\AndroidStudio2021.2
depending on your version and rename these folders:
caches to caches_old
compiler to compiler_old
compile-server to compile-server_old
conversion to conversion_old
external_build_system to external_build_system_old
frameworks to frameworks_old
gradle to gradle_old (if exists)
resource_folder_cache to resource_folder_cache_old (if exists)
Open Android Studio again and the autosuggsion will be fixed.
and You can also check if Power Save Mode is disabled or not from the File menu.
I want to see warnings of my code in Android Studio, But i am unable to find the option to display warnings view. In case of eclipse we can see the warnings in the "Problems" view.
Can anyone suggest me, how to view warnings in android studio?
If, on the toolbar, you click Analyze -> Inspect Code; then in the window that pops up select how much of your project you want to inspect (I usually do Whole Project, but you might want to select a specific module), then click okay.
Android Studio will work for a bit, then the inspection window will pop up from the bottom with a list of results, subdivided by inspection.
Build -> Make Project (Ctrl + F9) gives what we can get equivalent of Eclipse's “Problems” view on Android Studio
you can use F2 to next problems, see more here: Navigating to Next/Previous Error
GO to View-->Tool Windows-->Messages to view the warnings
Even i searched all the settings in Android Studio, but couldn't find a separate window for it.
The warnings are actually visible to the right end of a particular line as a small yellow marker and clicking on that show the warnings in the status bar below. The colors of them can be editted in the inspection options.
Hope this helps you.
The closest thing Android Studio/IntelliJ has to the Problems view in Eclipse is to use the Problems section of the Project tool window. With that open, navigate down to any classes that appear there and open them in the editor. Once in the editor, you can use F2 to jump between errors in the open file.
Unfortunately, IntelliJ's Problems tool window shows classes with errors nested by folder/package, so you have to expand several levels and it takes up a lot of screen real estate to see even one error. It also doesn't list the errors individually, forcing you to first open the problematic file and then use F2 to navigate to each one. I also had the problem that errors in files that weren't open, didn't show up there.
[opening warning screen in android studio
Click the warning icon as marked in the image.
Warning screen will open.
][click to see image] here
I have been using the customer preview of Visual Studio 2012 up until day before yesterday when the Release Candidate became available. After I installed the Release Candidate, I can't get to the Test Window (Test / Windows / Test Explorer).
I get the following lengthy error which I've copied manually here. (Since this is my first question, I couldn't post the picture, and the screen would not allow me to copy the text to the clipboard. Hopefully there are no typos.)
The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information.
1) Value cannot be null.
Parameter name: testPlatform
Resulting in: An exception occurred while trying to create an instance of type 'Microsoft.VisualStudio.TestWindow.Model.ReqeustConfigurationFactory'.
Resulting in: Cannot activate part
'Microsoft.VisualStudio.TestWindow.Model.ReqeustConfigurationFactory'.
Element: Microsoft.VisualStudio.TestWindow.Model.ReqeustConfigurationFactory -->
Microsoft.VisualStudio.TestWindow.Model.ReqeustConfigurationFactory --> CachedAssemblyCatalog
Resulting in: Cannot get export
Microsoft.VisualStudio.TestWindow.Model.ReqeustConfigurationFactory
(ContractName="Microsoft.VisualStudio.TestWindow.Model.RequestConfigurationFactory")' from part
'Microsoft.VisualStudio.TestWindow.Model.ReqeustConfigurationFactory'.
Element:
Microsoft.VisualStudio.TestWindow.Model.ReqeustConfigurationFactory
(ContractName="Microsoft.VisualStudio.TestWindow.Model.RequestConfigurationFactory") --> CachedAssemblyCatalog
The error occurs regardless of whether I have opened a solution or not. A second attempt to open the window yields "Cannot create the tool window." After restarting Visual Studio, and attempting to get to the Test Window, I get the long message again.
At the time I upgraded Visual Studio to the Release Candidate, I had installed:
NUnit
SpecFlow
ReSharper (Beta)
Code Contracts -- the last thing I had installed before upgrading Visual Studio. I cannot guarantee that the test window was working after I installed this.
I have searched the web for key phrases out of the error message, but found no help.
I have also:
Repaired Visual Studio (which solved a problem I was having getting to the Extension Manager, but not the Test Window problem)
Uninstalled Visual Studio and reinstalled it
Uninstalled each of the Extensions/packages listed above (NUnit, SpecFlow, ReSharper, Code Contracts). Uninstalling didn't seem to help, so I have re-installed all of them,
one at a time. I've also confirmed that I can run tests in the ReSharper test window.
Deleted the currentsettings.vssettings file from C:\Users\\Documents\Visual Studio 11\Settings, hoping it contained the problem and would be recreated correctly. I got a message that "The IDE will use your most recent settings for this session". I don't know where to find those...
Reset settings from the Import and Export Settings option.
None of these actions has helped.
It looks to me like a config file somewhere is missing an element for testPlatform, but I have no idea where that would be (or in what format, or what Options page entry would set it.)
Any help would GREATLY be appreciated.
I didn't figure out exactly what was causing the error, but I did get it fixed. Here's what finally worked
I installed all VS 2012 one more time, plus the extensions, then looked for bits that might have been left behind by the uninstall. I found and deleted the following before reinstalling:
C:\Users\<my id>\Documents\Visual Studio
C:\Users\<my id>\AppData\Roaming\Microsoft\VisualStudio
C:\Users\<my id>\AppData\Local\Microsoft
Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
Upon re-installing Visual Studio 2012 RC, the original problem was resolved. Re-installing the extensions also worked successfully.