Search Issue Tracker

Fixed in 2018.1.X

Fixed in 2017.4.X

Votes

6

Found in

2017.3.0p3

2017.3.0f3

Issue ID

991204

Regression

Yes

[iOS] Build fails with an error "DXT1 compressed textures are not supported when publishing to iPhone"

Mobile

-

Reproduction Steps:
1. Open User's project
2. Build to iOS
3. Notice that build failed

Errors:
DXT1 compressed textures are not supported when publishing to iPhone
Packages/com.unity.ads@2.0.3/Editor/Resources/Editor/landscape.jpg
Included from scene:
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

DXT1 compressed textures are not supported when publishing to iPhone
Packages/com.unity.ads@2.0.3/Editor/Resources/Editor/portrait.jpg
Included from scene:
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Expected behaviour: Build completes successfully

Reproduced on versions: Unity 2017.3.0f3, 2017.3.0p3
Did not reproduce on versions: Unity 2018.1.0b4, 2017.3.0f2, 2017.2.1p2
Log in to vote on this issue

Comments (37)

  1. peterpunk

    Jun 20, 2019 10:33

    Also there in Unity 2018.4.0, 2018.4.2, 2019.1.7 :-(

  2. arjenveenhuizen

    Mar 28, 2019 07:07

    Issue is still there on Unity 2018.3.0f2 for Linux. I have to manually reimport all affected assets through scripting code when building for iOS to work-around this problem
    AssetDatabase.ImportAsset("PATH_TO_ASSET",
    ImportAssetOptions.ForceUpdate);

  3. mobadu

    Feb 21, 2019 10:16

    Not fixed in 2018.2.18

  4. daniel_ys

    Jan 15, 2019 08:22

    This seems to be happening to us with a clean import of Unity IAP package into our project. Just doing that triggers the errors in all our images

  6. nilareguy

    Jan 09, 2019 22:14

    Right click in Project Assets folder and Reimport All fixed the issue for me.

  7. realitygarage

    Jan 08, 2019 21:06

    Also getting this w/ Unity 2018.3, as well as 2018.2.19 - but error message is DXT5 compressed textures are not supported when publishing to iPhone.

    Very frustrating!

  8. giorgos_gs

    Dec 28, 2018 11:40

    This issue is back in 2018.3 for mac, build ios

  9. StevenDelrue

    Dec 20, 2018 20:30

    Same issue in 2018.3.0f2 (in upgraded project from 2018.2)

    If I create a new project in 2018.3, import the assets again it's fixed

  10. jeffries7

    Dec 11, 2018 18:10

    I'm getting this issue in 2018.3.0F1(RC1) again.

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.

Latest issues

See all new issues