Search Issue Tracker
Duplicate
Votes
12
Found in [Package]
0.6.0-preview.7
Issue ID
1311658
Regression
No
[Netcode][IL2CPP][Android] Release build crashes on null pointer dereference when launching it
Steps to reproduce:
1. Open the user's attached project "GameplayServerTest.zip"
2. Navigate to Project window-> Build
3. Select Android-Client (Release)
4. Press the Build button at Inspector (built APK can be located in project path/Builds/Android-Client (Release))
5. Launch the app
Expected results: App launches
Actual results: App Crashes on start
Reproducible with: 2020.2.3f1
Unable to test with: 2018.4, 2019.4, 2021.2 due to errors in the project
Reproducible devices:
VLNQA00264, Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00279, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Note: LogCat Is attached in the edit field
Comments (3)
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
- Diagnostics logs are missing, duplicated, or out of order when viewing Player sessions in Cloud Diagnostics
- Prefab Overrides “Apply” button is too big and overlaps with the context menu’s outline
- Prefab Overrides “No Overrides” text is too large, and the the Context Menu of the Parent GameObject has a lot of empty space when opened
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
HuliganBear
Dec 18, 2021 14:27
@TWAANANEN I think this is the active ticket
https://issuetracker.unity3d.com/issues/dots-android-il2cpp-arm64-app-crashes-on-start-in-release-build
twaananen
Nov 12, 2021 17:39
1315007 is a duplicate of this, and this is a duplicate of? Where can we follow the progress on this fix?
unity_btkiGPiGhCEfIA
Sep 17, 2021 07:10
The same crash I've got on Android 11 and Samsung A12. Other Android 11 devices was not affected by this issue.