14
votes

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..

8
@GowthamanM As I said I tried this already.. If read my question completely you can saw this linkShailendra Madda
Any solution for this yet?Shailendra Madda

8 Answers

6
votes

Finally, I resolved by creating new Android project and moved my all files into it. This issue got because of existing settings in the old project.

It may useful for someone.

Update:

Go to File--> Project Structure --> Check Use Embedded JDK (Recommended)

Ref:enter image description here

3
votes

@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.

2
votes

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.

2
votes

Faced the same problem on v3.5.3. Resolved by deleting .idea folder.

1
votes

I had an issue related to the antivirus:

  1. If you want to do it the easy way: Windows Defender>Virus & Threat protection>Ransomware Protection> Unable the protection.
  2. 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\History Delete everything in that folder.
  3. 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.
0
votes

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.

0
votes

I found how to fix 1: go to window Defender security center. 2: click on Virus & threat protection. 3: Ransomware Protection. 4: do off the radio button.

[enter image description here][1] e.g [1]: https://i.stack.imgur.com/f75iB.png

0
votes

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.