Search Issue Tracker

Fixed in 2021.1.X

Fixed in 2019.4.X, 2020.3.X



Found in






Issue ID




[iOS] Unable to create Texture2D's with ASTC_RGBA_4x4 texture format at runtime



How to reproduce:
1. Open the attached '' project
2. Switch Platform to iOS in Build Settings
3. Build for iOS and open the Xcode project
4. Deploy Xcode project to an iOS device

Expected result: Texture with ASTC_RGBA_4x4 texture format is created
Actual result: Texture with ASTC_RGBA_4x4 texture format fallbacks to ASTC_RGB_4x4 and 'Texture creation failed. 'ASTC_RGBA_4x4' is not supported on this platform. Use 'SystemInfo.SupportsTextureFormat' C# API to check format support.' error is thrown

Reproducible with: 2019.1.0a1,2019.4.11f1, 2020.1.6f1, 2020.2.0b3
Not reproducible with: 2018.4.27f1

Reproducible on:
Mac Standalone
iPhone 8+ (iOS 12.0)
iPhone XR (iOS 13.4.1)
iPad Air 2 (iOS 11.0.3)
iPad 9.7 6th gen (iOS 14.0b7)
VLNQA00220, Samsung Galaxy Note9 (SM-N960F), Android 8.1.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android R, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00313, Huawei Y6 \xe2\x85\xa1 Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
----------, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: NOT FOUND, GPU: Mali-G77

- Reproducible with PVRTC_RGBA4, ASTC_RGBA_4x4 textures formats

  1. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.0a1. We have fixed the support for deprecated texture formats, but user should update api (it will work automatically)

  2. Resolution Note (fix version 2020.3):

    Fixed in: 2020.3.25f1

  3. Resolution Note (fix version 2019.4):

    Fixed in: 2019.4.34f1

Comments (2)

  1. allfake

    Dec 03, 2020 06:55

    I need this in 2019 LTS.
    (༎ຶ⌑༎ຶ) (༎ຶ⌑༎ຶ) (༎ຶ⌑༎ຶ) (༎ຶ⌑༎ຶ)

  2. jpetty7317

    Sep 24, 2020 14:07


    I am the original reporter of this issue and have been keeping track of this page and the original ticket as well for progress. I came back today to see the Resolution Note under the ticket description, and that it mentions an api update that should resolve it automatically. Can you speak more to this?

    I also notice, per the description in the ticket, that the issue is reproducible in the latest 2019 LTS and 2020.1.6. With a fix inbound, would you be able to say what patch release for 2019 LTS the fix will be in and when we can expect to see that build? Thank you in advance for any and all information, as it will be extremely helpful.

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.