Search Issue Tracker
Fixed in 2018.3.5f1
Votes
15
Found in
2018.2.16f1
2018.3.0b10
2019.1.0a5
2019.1.0a7
Issue ID
1095565
Regression
Yes
"ETC1 compressed textures are not supported when publishing to Standalone" error on build after switching platform from Android
Steps to reproduce:
1. Open attached "tdd-asteroids.zip" Unity project
2. Switch platform from Android to Standalone in Build Settings
3. Build project
Expected results: project builds successfully
Actual results: building fails with error "ETC1 compressed textures are not supported when publishing to Standalone"
Reproducible with: 2019.1.0a7, 2019.1.0a5, 2018.3.0b12, 2018.3.0b10, 2018.2.19f1, 2018.2.16f1 (39a4ac3d51f6)
Not reproducible with: 2019.1.0a4, 2018.3.0b9, 2018.2.16f1 (26a3312b6d5d), 2017.4.16f1
Regressed in: 2019.1.0a5, 2018.3.0b10, 2018.2.16f1 (39a4ac3d51f6)
Note: Upgrading project with platform set to Android from 2017.4 to 2019.1 and switching to Standalone platform in editor causes the builds to fail due to this error. Deleting the Library folder fixes the issue.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Sneeza
Jan 11, 2019 10:34
I'm having this issue in 2018.2.19f1 as well as 2019.1, but my issue solves temporarily by deleting the Library folder and almost immediately returns when swapping platforms. This is causing me serious headaches on a daily basis when I have to swap platforms to make builds for everything we support and forces me to re-import all of our textures manually which can take hours on my laptop.
This is a serious regression that started occurring when I upgraded our project to 2018 and needs to be addressed. If anyone has any ideas on a more permanent fix for this issue that would be incredible!
Markzs17
Dec 01, 2018 22:31
Same problem here with Unity 2018.2.17f1. Got it reproducible after switching back to Linux build settings after building the game for Android.
Got it solved by deleting the Library as suggested, thanks for the info!