Search Issue Tracker

Fixed

Votes

2

Found in

2019.2

2019.2.6f1

2019.3

2020.1

Issue ID

1190240

Regression

No

[iOS]Built in resource Default-Checker-Gray is compressed with DXT1, causes build to fail with errors when building for iOS

iOS

-

How to reproduce:
1. Open the attached project New Unity Project.zip
2. Built the project for iOS

Expected: Build succeeds
Actual: Build fails with errors (see the errors below)

Reproducible with: 2019.2.9f1, 2020.1.0a8

Not reproducible with: macOS, Windows, Android, WebGL platforms

Errors:
DXT1 compressed textures are not supported when publishing to iPhone
Resources/unity_builtin_extra
Included from scene:
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Building - Failed to write file: sharedassets0.assets
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

UnityEditor.BuildPlayerWindow+BuildMethodException: 4 errors
at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.BuildPlayer (UnityEditor.BuildPlayerOptions options) [0x00234] in /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:190
at UnityEditor.BuildPlayerWindow.CallBuildMethods (System.Boolean askForBuildLocation, UnityEditor.BuildOptions defaultBuildOptions) [0x0007f] in /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:96
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Note: Could not nest on 2017.4 and 2018.4 as the texture was added to the "Default textures" in 2019.1
The Build fails when Main Texture Albedo of the Material is to Default-Checker-Gray

Comments (3)

  1. Aabd2f7f55e2a64e175715e46fafa8c8?d=mm

    THDevelopment

    Jan 20, 2020 00:41

    Is there a solution for this one? We have the same problem with all Engine Versions (2017, 2018, 2019, 2020). We cannot find or delete the default-checker-gray file from our Project. No Files are referencing to it - just a few standard materials (but no default-checker-gray texture is attached to albedo)

    No clue why this error appears - and we tried out many differend things to fix it - no success.

    Help would be great - thank you very much!

  2. Cb05d0b08b65ceb6f065e67d9a18d923?d=mm

    siddhantb

    Jan 08, 2020 06:16

    2019.2.12f1 Same issue

  3. 57990e5870ed54b40923f8195427d4ff?d=mm

    hosanWon

    Nov 07, 2019 13:50

    2019.2.8 have same build error

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.