Copyright © 2026 Unity Technologies
No further releases planned for 2023.1
I'm adding a comment here on the bug, but it applies directly to the 2022.3 port because we cannot verify that the bug is fixed in that version. The problem is with the user code in the project for step 5: "Modify libil2cpp.so". That code emits some invalid data to the libil2cpp.so file, specifically giving us an elf here with a n_descsz field that is 131 bytes long. This means that the code does an unaligned read, which causes a crash on ARMv7 chips. This code was not modified for this bug fix, and it is correct, assuming that we have valid data in the libil2cpp.so file. So although we cannot verify this on 2022.3, we have verified the fix on other versions, and the crash is unrelated to the user's issue. Instead, the new crash is related to this bug in the code that tries to trigger the crash.
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Export the project to the “GradleProject” folder
4. Use Android Studio to open the project and build it
5. In Unity Editor Click "Tools -> Modify libil2cpp.so"
6. Click Run in Android Studio and observe the Player
Expected result: The Player launches successfully and continues to run
Actual result: Player crashes at launch
Reproducible with: 2021.3.29f1, 2022.3.7f1, 2023.1.8f1, 2023.2.0b4
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: Exynos 9 (9825), 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
Testing environment: Windows 10 Enterprise 21H2
Issues you vote on will appear here