Scope was not disposed! You should use the 'using' keyword or manually call Dispose. UnityEngine.Sco

I can't access the player settings for some reason, when I try to access it, the following error is spamming the console -

Code (CSharp):

1. Scope was not disposed! You should use the 'using' keyword or manually call Dispose.
2. UnityEngine.Scope:Finalize()

I did try to search a solution online but I got nothing, any help would be appreciated.

 

I'm having the same issue on Android's Player Settings. The two Unity versions causing this is 2019.2.0b5 (beta) and 2019.3.0a5 (alpha).

The stable release 2019.1.5f1 is working fine on that aspect so I recommended you use that one in case your version is one of the mentioned above.

 

Having this too with 2019.3.0a7

 

Same problem in version 2019.2.0f1.
I just wanted to expand the Icon tab, after that a lot of errors appeared in the console and the Player became unavailable. And the errors appear exactly when the Player tab is pressed.
I regret having updated to this version.

 

Same problem in version 2019.2.0f1. Player unavailable.

P.S. After "build and run" on my telephone, problem has gone.

 

Thank you It works!!

 

I can't build to the phone as I have to provide passwords for signing. Any other ideas?

 

same problem

 

I'm having the same problems as everyone here, I've just filed a bug report, so I guess all we can do it wait. I've tried all the different fixes people have suggested, but nothing is working for me.

 

It seems that to fix this bug you have to uninstall all the latest versions of Java (9 and above). If it's not Java 8 you will get issues. Try that and post back your results.

 

I've resolved the problem tonight. To get the Project Setting/Player to open again, you need to uninstall the Android Developer tools. Since I deleted them forcefully with no official way to re-import or uninstall, my projects a bit broken and I am uncertain as to which SDK I should use.

I filed a bug report as well and backtracked from what I mentioned in the report.

Using Unity 2019.2.2f1

 

A bit of a workaround. If you start exploring the Player options on other platforms (so IOS, PC) in the inspector and actually click on the tabs, then click on the Android icon in the inspector, the Android Player settings will work again. It will however break again once you click the Icon tab.

 

This worked for me

 

to fix this easily, just switch platform to pc and build. after that you can access into a player settings. you can too switch again to mobile platform

 

Just had the same issue while trying to compile for iOS on Mac (Unity 2019.2.10f1)

From the console:
"Scope was not disposed! You should use the 'using' keyword or manually call Dispose.
UnityEngine.Scope:Finalize() (at /Users/builduser/buildslave/unity/build/Modules/IMGUI/GUI.cs:1704)"

Bug and workaround:
It turned out that this was caused by having the "Project Settings" window open and undocked. As soon as I closed the window, compilation worked again without errors .

 

check android plugin if missing then install it other wise override on it. hope it's help full.

 

Thanks !

 

did you find its solution ?

 

@karl_jones
This happens when Projest Settings -> Script Execution Order window is open and I open another scene. First I see this errors:

Code (Boo):

1. MissingReferenceException: The object of type 'MonoScript' has been destroyed but you are still trying to access it.
2. Your script should either check if it is null or you should not destroy the object.
3. UnityEngine.Object.get_name () (at <05f2ac9c8847426992765a22ef6d94ca>:0)
4. UnityEditor.ScriptExecutionOrderInspector+DragReorderGUI.IsDefaultTimeElement (UnityEditor.MonoScript element) (at <17b72532ee2c4da1b6f632d3f1705fe0>:0)
5. UnityEditor.ScriptExecutionOrderInspector+DragReorderGUI.DragReorder (UnityEngine.Rect position, System.Int32 elementHeight, System.Collections.Generic.List`1[T] elements, UnityEditor.ScriptExecutionOrderInspector+DragReorderGUI+DrawElementDelegate drawElementDelegate) (at <17b72532ee2c4da1b6f632d3f1705fe0>:0)
6. UnityEditor.ScriptExecutionOrderInspector.OnInspectorGUI () (at <17b72532ee2c4da1b6f632d3f1705fe0>:0)
7. UnityEditor.AssetSettingsProvider.OnGUI (System.String searchContext) (at <17b72532ee2c4da1b6f632d3f1705fe0>:0)
8. UnityEditor.SettingsWindow.DrawControls () (at <17b72532ee2c4da1b6f632d3f1705fe0>:0)
9. UnityEditor.SettingsWindow.DrawSettingsPanel () (at <17b72532ee2c4da1b6f632d3f1705fe0>:0)
10. UnityEngine.UIElements.IMGUIContainer.DoOnGUI (UnityEngine.Event evt, UnityEngine.Matrix4x4 parentTransform, UnityEngine.Rect clippingRect, System.Boolean isComputingLayout, UnityEngine.Rect layoutSize, System.Action onGUIHandler, System.Boolean canAffectFocus) (at <7be1a95b44f5474c9c1a5c5fd9c86b28>:0)
11. UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Then when I open another scene again I see these:

 

Where can I do it?

 

It happened the same to me with 2019.3.13. Following the lead of somebody here I closed the Projects Settings (The window that Opens from Edit > Project Settings), and I was able to compile my Android game again.

 

Just had the same error on Unity 2019.3.7f1 on MacOS10.15.5

Scope was not disposed! You should use the 'using' keyword or manually call Dispose.UnityEngine.Scope:Finalize()​

Closing windows, building, rebooting didn't work ...

SOLVED I'm building for iOS and I found that:
disabling Metal Editor Support changes the editor API (restarts Editor) then re-enabled Metal support (restarts Editor again) and the errors went away.

 

its seem to very late but may be it can help for someone else
i just switch the platform then build then everything work properly

 

it was to late for reply but if u stuck in this problem just switch platform then go to the player setting and reset the player setting then go back to your platform and check player setting you will see every thing work's

 

thank you for your comment it help me and problem solved

 

Had the same issue in 2019.3.10f1 and like the comment above the project settings window (docked or undocked didn't make difference) was the reason for the exceptions. Closing the settings tab or just opening another tab fixed it for me.

EDIT: it was the script execution order setting in particular which was open in my project settings tab