Search Issue Tracker

Fixed in 2018.2.X

Fixed in 2017.2.X, 2017.3.X, 2018.1.X

Votes

13

Found in

2017.1.0f3

Issue ID

935292

Regression

No

[Android][.Net 4.6] HTTPClient.GetAsync fails to get address with unable to find libc error

Android

-

To reproduce:

1. Download and open attached "GetDomainNameAndroidBug.zip" project.
2. Enter play mode and notice Debug.log statements printed out.
3. Exit play mode.
4. Build and run with android device connected.
5. Use logcat to see application logs.
6. Notice that logs differ. Connection error appears.

Expected result: Everything works the same as in the editor. Connection to client address succeeds.
Actual result: "Unable to find libc" error appears. Connection doesn't succeed.

Reproduced with: 2017.3.0a2, 2017.2.b5, 2017.1.0p2.

Devices under test:

Samsung SM G925F (Galaxy S6 Edge)*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760,
Build:samsung/zeroltexx/zerolte:7.0/NRD90M/G925FXXU5EQFC:user/release-keys

Google Nexus 6*, OS:6.0.1, CPU:armeabi-v7a, GPU:Adreno (TM) 420,
Build:google/shamu/shamu:6.0.1/MOB30O/2920157:user/release-keys

Sony C6603 (Xperia Z)*, OS:5.1.1, CPU:armeabi-v7a, GPU:Adreno (TM) 320,
Build:Sony/C6603/C6603:5.1.1/10.7.A.0.228/58103698:user/release-keys

Notes: Feature works only with .Net 4.6. On standalone everything works correctly. On iOS some of the logs seems to be missing but no there are no errors printed.

Verified with: 2018.2.0a1, 2018.1.0b7, 2017.3.1p1, 2017.2.1p4

For fix to work, in Player settings "Internet Access" property must be set to Require. Also "Unable to find libc" error can still be seen in the logcat, thus the initial problem that connection did not succeed was fixed.

Comments (81)

  1. OC01

    Oct 30, 2017 06:55

    I got the same error when I used `CookieContainer` class.
    in Unity 2017.3.0b6

    Devices: Huawei SCL-L02, Galaxy SC-04E

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.