Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.4
2019.4.11f1
2020.2
Issue ID
1283096
Regression
No
[Android] Native errors show up after starting the App
How to reproduce:
1. Open the attached "USDKInitializer_Repro.zip" Project
2. Make sure "Android" target is selected
3. Build and run the App on an Android device
Expected Behavior: No errors are present in the Logcat
Actual Behavior: Native libraries display errors
Reproducible with: 2019.4.12f1, 2020.1.8f1, 2020.2.0b7
Could not test with: 2018.4 due to build errors
Reproducible devices:
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
Devices could not test with(due to device logcat not working):
VLNQA00286, Meizu - (PRO 5), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
Note: According to the customer the errors do not affect the functionality. Attached the Logcat.log to this case.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment