Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assertion failed UnityEditor.RetainedMode:UpdateSchedulers #1786

Closed
Volodymyr-13 opened this issue Oct 4, 2021 · 11 comments
Closed

Assertion failed UnityEditor.RetainedMode:UpdateSchedulers #1786

Volodymyr-13 opened this issue Oct 4, 2021 · 11 comments
Assignees
Labels
P1 Priority issue.

Comments

@Volodymyr-13
Copy link

Volodymyr-13 commented Oct 4, 2021

[REQUIRED] Step 1: Describe your environment

  • Unity version: 2020.3.19f1
  • Google Mobile Ads Unity plugin version: 6.1.1
  • Platform: iOS, Unity Editor
  • Platform OS version: Big Sur 11.6 (20G165)
  • Any specific devices issue occurs on: editor
  • Mediation ad networks used, and their versions: AdColony 2.3.0, Applovin 5.1.1, Facebook Audience Network
    3.4.0, IronSource 2.1.1, Tapjoy 2.7.0, Unity Ads 2.7.2, Vungle 3.6.0

[REQUIRED] Step 2: Describe the problem

Steps to reproduce:

We integrated 6.1.0 with all that mediation networks and submitted production build. All ok, all works as expected.

Then we tried to update to 6.1.1, update was like okay, but then we tried to build Xcode project - got error:
Screenshot 2

Clicked - Open Settings gave us iOS/android ID's now empty.
Well, we filled them again, build project, build ok. Then close Unity and check for file modifications on git:

Screenshot

As you can see, after update of Admob to 6.1.1 it's wiped out project ID's, even after we entered them manually and saved project.

So, again we just tried to select file in editor GoogleMobileAdsSettings.asset and got 999+ errors:
Assertion failed
UnityEditor.RetainedMode:UpdateSchedulers () (at /Users/bokken/buildslave/unity/build/External/MirroredPackageSources/com.unity.ui/Editor/RetainedMode.cs:50)

Screenshot 1

So, in short steps was:

  • update admob - it's wiped ID's, ok, we re-enter ID's again in GoogleMobileAdsSettings.asset file
  • close/open project, to check if ID's actually saved(also we tried in menu Unity: File -> Save Project)
  • select GoogleMobileAdsSettings.asset cause 999+ errors,

Unable to edit this file now, always errors if we try to select it or if we try to build Xcode project.

@Bagdaja
Copy link

Bagdaja commented Oct 4, 2021

Have you tried downgrading the admob version? I've tried and when selecting GoogleMobileAdsSettings.asset it didn't show any errors, but when trying to play in the editor unity will simply crash

@Volodymyr-13
Copy link
Author

We just reverted commit in our project with latest update try to 6.1.1
We don’t see any reason to use broken version in our production releases.

@sammorris-fss
Copy link

We're getting the same thing here. Unity 2020.3.19 and plugin version 6.1.1. Makes the SDK entirely unusable.

@96698041
Copy link

96698041 commented Oct 5, 2021

Same to me!
Editor: 2020.3.19f1 - Windows,
Platform: Android,
Admob plugin version: 6.1.1
Error: It's wiped out project ID's, even after we entered them manually and saved project and selecting file in editor GoogleMobileAdsSettings.asset... 999+ errors Assertion failed: UnityEditor.RetainedMode:UpdateSchedulers ()

@Volodymyr-13
Copy link
Author

@NVentimiglia one more highest priority.

@NVentimiglia NVentimiglia self-assigned this Oct 7, 2021
@NVentimiglia NVentimiglia added the P1 Priority issue. label Oct 7, 2021
@Mykaelos
Copy link

Mykaelos commented Oct 16, 2021

I'm running into the same issue (first time using the plugin, so I was really confused why the AppID wasn't being saved).

Unity 2020.1.5f1
Plugin 6.1.1

For me, there's an initial exception when loading the GoogleMobileAdsSettings.asset and then the endless Assertion failed errors. It seems that the GoogleMobileAdsSettings are being loaded/created while Unity is still doing UI stuff, which is causing the InvalidOperationException.

I can trigger the error somewhat consistently by closing/opening Unity, and then opening the Google Mobile Ads Settings (Assets > Google Mobile Ads > Settings).

Edit/Update: I reverted to 6.1.0 and it's working fine, so it's definitely a change that happened in 6.1.1.

InvalidOperationException: Hierarchy change detected while computing layout, this is not supported.
UnityEngine.UIElements.UIRLayoutUpdater.OnVersionChanged (UnityEngine.UIElements.VisualElement ve, UnityEngine.UIElements.VersionChangeType versionChangeType) (at <e11cddb636f444f68eec62123764f018>:0)
UnityEngine.UIElements.VisualTreeUpdater.OnVersionChanged (UnityEngine.UIElements.VisualElement ve, UnityEngine.UIElements.VersionChangeType versionChangeType) (at <e11cddb636f444f68eec62123764f018>:0)
UnityEngine.UIElements.Panel.OnVersionChanged (UnityEngine.UIElements.VisualElement ve, UnityEngine.UIElements.VersionChangeType versionChangeType) (at <e11cddb636f444f68eec62123764f018>:0)
UnityEngine.UIElements.VisualElement+Hierarchy.Clear () (at <e11cddb636f444f68eec62123764f018>:0)
UnityEngine.UIElements.VisualElement.Clear () (at <e11cddb636f444f68eec62123764f018>:0)
UnityEditor.PropertyEditor.RebuildContentsContainers () (at <6d0b5326886a4f0e8ed4ea356b37330b>:0)
UnityEditor.InspectorWindow.RedrawFromNative () (at <6d0b5326886a4f0e8ed4ea356b37330b>:0)
UnityEditor.AssetDatabase:CreateAsset(Object, String)
GoogleMobileAds.Editor.GoogleMobileAdsSettings:get_Instance() (at Assets/GoogleMobileAds/Editor/GoogleMobileAdsSettings.cs:68)
GoogleMobileAds.Editor.GoogleMobileAdsSettingsEditor:OnInspectorGUI() (at Assets/GoogleMobileAds/Editor/GoogleMobileAdsSettingsEditor.cs:22)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)

Assertion failed
UnityEditor.RetainedMode:UpdateSchedulers()
...

@yerfdogj
Copy link

Related with fixes:
#1796
#1801

@NVentimiglia
Copy link
Member

Pushed a release 6.1.2 which should solve the issue. Please let me know if you run into any further issues.

https://github.com/googleads/googleads-mobile-unity/releases/tag/v6.1.2

@ghost
Copy link

ghost commented Oct 20, 2021

@NVentimiglia
just so you know, this patch doesn't solve #1801
Atm. the GoogleMobileAdsSettings can't be used without changing code yourself

@Volodymyr-13
Copy link
Author

@TheGoodEvilBen For me it's fixed now in 6.1.2.
What exactly do you mean by - "can't be used" ?
I can select settings and now it's not wiped and saved correctly.

@xtrecoolx
Copy link

The issue still exists for Android. Admob settings are not saved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority issue.
Projects
None yet
Development

No branches or pull requests

8 participants