Search Issue Tracker
Fix In Review for 2019.3
Votes
36
Found in
2018.1.0b13
Issue ID
1022228
Regression
No
[Android][Mono][IL2CPP] "Unable to find libc" error thrown when executing certain SslStream constructor
How to reproduce:
1. Open user attached project
2. Build to Android device
3. Run the logcat and run the application
Result: "Unable to lookup library path for 'libc', native render plugin support disabled" and "Unable to find libc" errors can be seen once executing the SslStream constructor at launch
Reproducible with - 2018.2.0b2, 2018.1.0f2, 2017.4.2f2, 2017.3.0a1
Notes:
1. Reproduced this with both IL2CPP and Mono with .NET 4.6
2. Did not reproduce the error with .NET 3.5
DUT:
Reproducible with:
Google Pixel 2 XL*, OS:8.1.0, CPU:arm64-v8a, GPU:Adreno (TM) 540, Build:google/taimen/taimen:8.1.0/OPM1.171019.011/4448085:user/release-keys
Samsung SM G930F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T880, Build:samsung/heroltexx/herolte:7.0/NRD90M/G930FXXU1DQC4:user/release-keys
Samsung SM G903F*, OS:6.0.1, CPU:armeabi-v7a, GPU:Mali-T720, Build:samsung/s5neoltexx/s5neolte:6.0.1/MMB29K/G903FXXU1BQC1:user/release-keys
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
- Custom Inspectors OnDisable still called after Asset has been deleted
- Native Plugin regression from 2018.x results in "DllNotFoundException" error
- [Android] "AndroidETC2FallbackOverride.Quality32BitDownscaled" does not work on an Atlas created with the Legacy Sprite Packer
- Debug.Log() Context not highlighted when pressed after printing in Test Runner's EditMode
- [Terrain] Painting on newly created neighboring terrains results in null reference errors
jfawcett
Jun 06, 2019 02:32
Hey everyone, I figured this out. More truthfully, the guy at RenderHeads that answered my post figured it out.
Under Plugins/Android/Libs/arm64-v8a, highlight each file in the inspector. Make sure the file is targeted for Android and ARM64. None of the files in my folder were targeted.
I also made sure I was only building for ARM64. Somehow I'd gotten ARM-7 checked too.
Built and deployed without problems.
Just passing this along, really. The guy to thank is AndrewRH at Renderheads.
Have fun!
John
MagnusJ
May 17, 2019 18:25
Same here. reproducible on Nexus 7 and a bunch of other devices:
Unity 2019.1.3f1
Auto Graphics API enabled
Scripting Runtime Version: ".NET 4.x Equivalent"
Scripting Backend: "Mono"
Api compatibility level: ".Net Standard 2.0"
After the Unity splash screen, just a black screen of death with this logged in Logcat:
(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 48)
05-17 20:18:23.001 15366-15419/? E/Unity: Unable to find libc
FunRobDev
Apr 25, 2019 21:28
"Unable to find libc" exeption logged in Android Device Monitor/LogCat
Sometimes the whole app freezes and not responding more!
Apk built by Unity 2019.1.0f2 (64-bit) ,
Scripting Runtime Version: ".NET 4.x Equivalent"
Scripting Backend: "Mono"
Api compatibility level: ".Net Standard 2.0"
Managed Stripping level: "disabled"
c:\Program Files\Unity\Hub\Editor\2019.1.0f2\Editor\Data\MonoBleedingEdge\lib\mono\4.5\System.ServiceModel.Web.dll
c:\Program Files\Unity\Hub\Editor\2019.1.0f2\Editor\Data\MonoBleedingEdge\lib\mono\4.5\System.ServiceModel.dll
are copied under Asset folder to compile code which class WCF/REST service.
Please fix this bug!
NGC6543
Feb 22, 2019 01:51
I was able to reproduce the "Unable to find libc" on Unity2019.1.0b4 + LWRP v5.3.1 on Android Device with OpenGLES2.0 Graphics API.
ZDestructor
Jan 25, 2019 20:15
I'm getting the error "Unable to find libc" with 2018.3.3. It happens during app startup, and the app eventually crashes with no other useful error messages.
jfawcett
Nov 20, 2018 01:36
Still there in 2018.2.16f1
SketchWork
Oct 14, 2018 18:45
And in 2018.2.12f1
derroboter
Sep 24, 2018 12:42
I can confirm that version 2018.2.5f1 has the bug
derroboter
Sep 24, 2018 12:42
I can confirm that version 2018.2.5f1 has the bug
gfsdfg
Sep 24, 2018 12:38
also found in 2018.2.5f1