Unity-Technologies/UnityCsReference · error · NotSupportedException

PlayerSettings.storeLargeTile80 is deprecated. Use GetVisual

Error message

PlayerSettings.storeLargeTile80 is deprecated. Use GetVisualAssetsImage() instead.

What it means

PlayerSettings.WSA.storeLargeTile80 is a deprecated static property getter that always throws NotSupportedException. Unity replaced the legacy per-scale Windows 8.1 tile-image properties with a unified GetVisualAssetsImage(WSAImageType, WSAImageScale) API. The property is [Obsolete(..., true)] (compile error) and [EditorBrowsable(Never)] (hidden from IntelliSense).

Source

Thrown at Editor/Mono/PlayerSettingsWSA.cs:401

            public static string storeSmallTile180
            {
                get
                {
                    throw new NotSupportedException("PlayerSettings.storeSmallTile180 is deprecated. Use GetVisualAssetsImage() instead.");
                }
                set
                {
                    throw new NotSupportedException("PlayerSettings.storeSmallTile180 is deprecated. Use SetVisualAssetsImage() instead.");
                }
            }

            [System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrowsableState.Never)]
            [Obsolete("Use GetVisualAssetsImage()/SetVisualAssetsImage()", true)]
            public static string storeLargeTile80
            {
                get
                {
                    throw new NotSupportedException("PlayerSettings.storeLargeTile80 is deprecated. Use GetVisualAssetsImage() instead.");
                }
                set
                {
                    throw new NotSupportedException("PlayerSettings.storeLargeTile80 is deprecated. Use SetVisualAssetsImage() instead.");
                }
            }

            [System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrowsableState.Never)]
            [Obsolete("Use GetVisualAssetsImage()/SetVisualAssetsImage()", true)]
            public static string storeLargeTile
            {
                get
                {
                    throw new NotSupportedException("PlayerSettings.storeLargeTile is deprecated. Use GetVisualAssetsImage() instead.");
                }
                set
                {
                    throw new NotSupportedException("PlayerSettings.storeLargeTile is deprecated. Use SetVisualAssetsImage() instead.");

View on GitHub (pinned to 225b0fbdb5)

Solutions

Replace the read with PlayerSettings.WSA.GetVisualAssetsImage(WSAImageType.UWPSquare150x150Logo, WSAImageScale._100) — the 80% legacy scale has no exact UWP equivalent, use _100 as the baseline.
Migrate all call sites referencing storeLargeTile80 in the project and any imported packages.
If the call originates from a plugin DLL, check for an updated version compatible with the current Unity version.

Example fix

// before
string path = PlayerSettings.WSA.storeLargeTile80;

// after
string path = PlayerSettings.WSA.GetVisualAssetsImage(WSAImageType.UWPSquare150x150Logo, WSAImageScale._100);

Defensive patterns

Strategy: type-guard

Validate before calling

// Prefer the new getter API unconditionally in modern Unity
string path = PlayerSettings.WSA.GetVisualAssetsImage(WSAImageType.UWPSquare150x150Logo, WSAImageScale._100);

Type guard

static bool IsDeprecatedWsaProperty(string name) =>
    typeof(PlayerSettings.WSA)
        .GetProperty(name,
            System.Reflection.BindingFlags.Public | System.Reflection.BindingFlags.Static)
        ?.GetCustomAttribute<ObsoleteAttribute>()?.IsError == true;

Prevention

Replace all storeLargeTile80 reads with GetVisualAssetsImage(WSAImageType.UWPSquare150x150Logo, WSAImageScale._100).
When using reflection to enumerate PlayerSettings.WSA properties, filter out members marked [Obsolete(..., true)] before accessing them.
Run a deprecation audit after every Unity version upgrade.

When it happens

Trigger: Reading PlayerSettings.WSA.storeLargeTile80 (the getter) — typically in editor scripts that query the current large tile asset path, build-report generators, or serialization code. Most commonly hit through reflection or SerializedProperty access since direct C# compilation fails.

Common situations: Porting a Windows 8.1 / Windows Phone 8 build pipeline to UWP; using legacy editor extensions that enumerate PlayerSettings properties; upgrading Unity and finding that a plugin still reads the old property.

Related errors

AI-assisted analysis of Unity-Technologies/UnityCsReference@225b0fbdb5 (2026-08-13). Data as JSON: /api/errors/657b29528c220648. Report an issue: GitHub.