Search Issue Tracker


Fixed in 2023.1.0a23



Found in





Issue ID




[Android] In logcat, Strip Engine code is falsely reported as being on when it's off



Steps to reproduce:
1. Open the attached project and make sure code stripping is disabled (Strip Engine Code setting in Player Settings > Other Settings)

2. Export gradle project

3. In override cmd line args (required to crash handler changes in trunk)



protected String updateUnityCommandLineArguments(String cmdLine)

{       return "-androidChainedSignalHandlerBehavior legacy"; }



4. Build and run from Android Studio on Android <8 device
5. Click the "ForcedCrashCategory.AccessViolation"
6. After application has crashed, check the logcat for "Code Stripping" entries

Expected: Code stripping is reportedly off, when it's off
Actual: Code stripping is reported as on, despite being off

Reproduced on: 2021.2.15f1, 2022.1.0b11, 2022.2.0a9

Reproduced on devices:
VLNQA00011 - Xiaomi Mi 5s (MI 5s), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 6.0.1
VLNQA00078 - Motorola Nexus 6 (Nexus 6), CPU: Snapdragon 805 APQ8084AB, GPU: Adreno 420, OS: 7.1.1
VLNQA00010 - Samsung Galaxy S8 USA (SM-G950U), CPU: Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 7.0.0

Note1: Mono is not using code stripping, therefore reported as off
Note2: Android 8+ devices no longer are able to add extra lines to the tombstone
Note3: Happens with both ARMv7 and ARM64, and developer/release modes

  1. Resolution Note (fix version 2023.1.0a23):

    Strip Engine Code information will be correctly printed for for unhandled java exceptions

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.