Search Issue Tracker

Fixed in 2018.1.X

Fixed in 2017.3.X

Votes

20

Found in

5.5.0a6

Issue ID

826788

Regression

Yes

"corrupted scene: Failed to unload 'ProjectSettings/UnityAdsSettings.asset" error in console

Scene Management

-

To reproduce:
1. Open attached project
2. Notice the error: "corrupted scene: Failed to unload 'ProjectSettings/UnityAdsSettings.asset"

Fixed in: 2018.1.0a4

Reproduced in 5.5.0b1
Not reproduced in 5.4.0p2

Comments (11)

  1. supasheva

    Dec 23, 2017 18:50

    Hi I am getting this error in 5.5.4p4. It also started after i did an upgrade

  2. b1naryatr0phy

    Mar 26, 2017 04:32

    Got this after updating 5.4.0f1 to 5.6.0b6

    Simply restarting Unity resolved it for me.

  3. joseruizmx

    Mar 14, 2017 17:29

    This work for me...

    5.4.3f1 to 5.5.2f1

    1. Close current project
    2. Create a new project
    3. Reopen your project

  4. Filipo6

    Jan 22, 2017 13:02

    Restarting Unity should fix the error.

  5. jdscogin

    Dec 31, 2016 12:41

    Maybe another clue. In Library/shadercompiler-UnityShaderCompiler.exe0 I found this error:
    Base path: H:/Unity/Editor/Data
    Cmd: getPlatforms
    Unhandled exception: Protocol error - failed to read correct magic number

    Quitting shader compiler process

  6. adi4x

    Dec 25, 2016 09:14

    A simple fix that worked for me and fixed this error + some particle errors (not found shader).
    For me the error started after upgrading from Unity 5.4.3f1 (64-bit) to Unity 5.5.0f3 (64-bit)

    1. Close current project
    2. Create a new project
    3. Reopen your project

  7. adi4x

    Dec 25, 2016 09:05

    Failed to unload 'ProjectSettings/UnityAdsSettings.asset'

    Unity 5.5.0f3 (64-bit)

  8. WagDan

    Dec 08, 2016 15:56

    Also in 5.5.0p1 - not using ads, but getting error message

  9. scruff311

    Dec 06, 2016 21:51

    Yup. Don't use ads but started getting this error when opening a project built with 5.3.2 in 5.5.

  10. Maakep

    Dec 02, 2016 22:19

    Don't use ads, never touched it. Got this when upgrading from 5.4.1f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.