Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.0b1
Issue ID
1082131
Regression
No
[Android] Incorrect bit patterns are being printed when using IL2CPP in the Android build
To reproduce:
1. Open attached project
2. Make sure to build with IL2CPP
3. Build and run to Android device
4. Check logcat for the incorrect bit pattern
Actual result: Building with IL2CPP prints "11001010"
Expected result: Building with IL2CPP should print "11100101"
Reproduced in:2018.3.0a10; 2018.3.0b1; 2018.3.0b2; 2019.1.0a1
Note: Due to errors can't reproduce on lower versions.
Tested with:
VLNQA00153, Google Pixel XL (Pixel XL), Android 8.0.0, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00173, Xiaomi Redmi 6Pro (Redmi 6 Pro), Android 8.1.0, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
Note: Building with mono, bit patterns are correct.
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
This is a duplicate of issue #1077373