Search Issue Tracker
Fixed in 2020.3.46f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a2
Votes
0
Found in
2020.3.44f1
2021.3.16f1
2022.2.2f1
2023.1.0a25
2023.2.0a1
Issue ID
UUM-25488
Regression
No
Crash on the unknown line when building a specific project
Reproduction steps:
- Open the attached project "flight simulator"
- Build And Run on an Android device
Expected result: APK is built successfully
Actual result: Editor crashes
Reproducible with: 2021.3.16f1, 2020.3.44f1, 2022.2.2f1, 2023.1.0a25
Reproducible with devices:
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
Reproduced on: Windows 10 Enterprise 21H2
Notes:
- Could not get Stacktrace
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
- Scaled Backgrounds List and dropdown text are enabled while Scaled Backgrounds field is disabled in IMGUI Debugger window
- Editor crashes when large value is entered in Scaled Backgrounds field of IMGUI Debugger window
- "Custom Function" Node "Input" type changes do not immediately show mistmatch errors when set to an incompatible type in Shader Graph
- My Assets list is populated with Asset Packages when setting how many Packages to display before clicking the Load button
- Hub shows 6.0 as Latest LTS when opening a project after deleting its 6.3 Editor version
Resolution Note (fix version 2023.2):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.
Resolution Note (fix version 2023.1):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.
Resolution Note (fix version 2022.2):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.
Resolution Note (fix version 2021.3):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.
Resolution Note (fix version 2020.3):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.