Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2017.3.1f1
Issue ID
1036625
Regression
No
[Android] AndroidJavaProxy causes AndroidJavaException when a byte array argument is passed
Steps to reproduce:
1. Open user attached project
2. Export Android project using the build system of Unity
3. Open exported project on Android studio and run it on an attached device
4. Observe that logcat prints "AndroidJavaException: java.lang.NoSuchMethodError: no non-static method with name='getLength' signature='(L[B;)I' in class Ljava.lang.Object;"
Expected result: AndroidJavaProxy should not cause AndroidJavaException when a byte array argument is passed
Reproduced in: 2018.3.0a1, 2018.2.0b5, 2018.1.2f1, 2017.4.3f1, 2017.3.1p3, 2017.2.3f1, 2017.1.3p2
Tested with:
Sony Xperia Z2, Android 6.0
HTC One mini 2, Android 4.4
Samsung Galaxy S5 mini, Android 6.0
Fixed in: 2018.3.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment