Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.41f1
2021.3.14f1
2022.1.23f1
2022.2.0b15
2023.1.0a20
2023.2.0a1
Issue ID
UUM-19359
Regression
No
“ArgumentException: May only be called in OnPostProcessTexture” errors are thrown when selecting the “Windows, Mac, Linux settings” on .png file in the Inspector window
Reproduction steps:
# Open the attached project
# Select the “Assets/Sprites/horizontalStrip2.png” file in the Project window
# Select the “Windows, Mac, Linux settings” tab (Monitor Icon) at the bottom of the Inspector window
# Observe the Console window
Expected result: No errors are present
Actual result: A lot of “ArgumentException: May only be called in OnPostProcessTexture” errors are thrown and the Inspector window freezes
Reproducible with: 2020.3.41f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a20
Reproducible on: Windows 10
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Thank you for reporting a bug to Unity.
The issue arises from a failed texture import, of which the user is sufficiently notified. Despite the Inspector freezing up locally, the user is still able to select other assets and continue working. After providing a valid texture for the broken asset, the error no longer happens.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.