'Android Studio 3.0 - Unable to save settings: Failed to save settings. Please restart Android Studio
Yesterday I was updated my Android Studio version to stable version 3.0 then I am started getting this errors in my studio and unable to build the app.
Unable to save plugin settings: The plugin org.jetbrains.android failed to save settings and has been disabled. Please restart Android Studio
But I forcefully enabled all plugins in my Studio by going to File-->Settings-->Plugins --> All are enabled.
I tried by deleting .AndroidStudio/* folder as suggested here and here
I tried by Invalidate and Restart and Enable Android Support as suggested here
And also tried by uninstalling studio and reinstalled latest stable version 3.0 one from here
But none of them are working, Can any one suggest me any alternate solution for this.
Thanks in Advance..
Solution 1:[1]
@DSlomer64
I found an easier way.
Instead of 'creating new Android project and moved my all files into it' as Shylendra Madda did, I merely deleted the .idea folder.
1) Go to File--> Settings -->Plugins Disable any plugins not loaded (i.e. red in color)
2) Enable the one plugin, Android Support
3) Right-click on your 'app' directory (contains your module gradle.build file) in Android Studio and select 'Show in Explorer' --- this opens that directory.
4) Quit Android Studio. Get out of any and all instances of Android Studio to allow you to then delete the fold, .idea, in that directory.
5) Restart AS, you'll notice the project will not come up -- you'll have to pick in the dialog window that appears. That's ok. Pick it, and it will 'rebuild' the folder, .idea.
6) Go to File--> Settings -->Plugins Enable any and all plugins
7) You won't get the message ever again... ;)
Cheers.
Solution 2:[2]
I had an issue related to the antivirus:
- If you want to do it the easy way: Windows Defender>Virus & Threat protection>Ransomware Protection> Unable the protection.
- If you want to do it the best way (considering your security):
Windows Defender>Virus & Threat protection>Ransomware Protection> APP through
monitored folder access> Add allowed APP> last blocked app> Add the
Studio64/Studio.exe (You need to enable hidden folders in order to open ProgramData)
Then, go to your Windows Explorer
C:\ProgramData\Microsoft\Windows Defender\Scans\HistoryDelete everything in that folder. - Check if your project's folder is in the exclusions folder. Windows Defender> Virus & Threat protection> Virus & threat protection settings> Add or remove exclusions. Android Studio should work fine now :D.
Solution 3:[3]
I think this problem is because your project in a drive that you don't have sufficient permissions to access. I faced that problem so I recreate my project in home directory (Ubuntu) instead ntfs drive and the problem is gone.
Solution 4:[4]
Faced the same problem on v3.5.3. Resolved by deleting .idea folder.
Solution 5:[5]
For me, because I installed the plugin that cause my AS error. mine AS 4.1.
How to trace the plugin issue
First, go to idea.log, it is located at
AppData\Local\Google\AndroidStudio4.1\logor you can use help -> show log in explorerCheck what cause the error, for me it is because plugin i installed from balloon tip for my NDK project (Android.MK) it is called dockdockgo. here is the error I got
java.lang.NoClassDefFoundError: Could not initialize class name.kropp.intellij.makefile.MakefileTargetKeyIndexKtAfter you got what makes you AS problem then delete the plugin at
AppData\Roaming\Google\AndroidStudio4.1\plugins
I have check that the plugins cause AS freezing from here and here. Lesson learned, never install plugin recommendation from balloon tips unless you have do some research with the plugins first.
Solution 6:[6]
Solution 7:[7]
You can try this:
- Rename the folder where the project is in
- Open the project in Android Studio (now you'll have to browse for it)
- Wait until it's synced and close the project
- Rename the folder back to original
That solved it for me. Just deleting the idea folder and invalidating caches did not solve the problem.
Solution 8:[8]
In my case it was the .idea\workspace.xml file that was not saved properly (presumably). There were two files: workspace.xml and workspace.xml~
I just renamed: workspace.xml to workspace-old.xml and workspace.xml~ to workspace.xml
And things were back to normal.
Solution 9:[9]
On MacOS: Open
- Terminal
- cd your_project_folder
- sudo chmod -R 777 ./
That means you are giving full permission to your project folder. You can modify permission level like 644, 755 etc.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Andrious Solutions |
| Solution 2 | |
| Solution 3 | |
| Solution 4 | yaugenka |
| Solution 5 | Yohanim |
| Solution 6 | double-beep |
| Solution 7 | Martin B |
| Solution 8 | Dave Enstrom |
| Solution 9 | XpressGeek |

