Search Issue Tracker

Fixed in 2018.1.X

Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X



Found in


Issue ID




UnityWebRequest GetResponseHeaders method returns null on Android devices



Reproduction steps:
1) Download and open user's attached project
2) Build and run test.unity scene on an Android device
3) Observe logcat
-- Notice that GetResponseHeaders() "response header is null" is being printed

Reproduced with:
5.6.3p4, 5.6.4f1, 2017.1.2f1, 2017.2.0f3, 2017.3.0b4
Unable to reproduce with:
5.6.3p3, 5.5.5f1
Regression appeared in 5.6.3p4

Reproduced with:
LG G4, Android 6.0
Huawei P9, Android 7.0
Samsung Galaxy S8, Android 8.0

Comments (8)

  1. guneyozsan

    Oct 19, 2018 19:21

    WebGL builds on 2018.2.11f1 have the same issue and GetResponseHeaders returns null. Can it be an IL2CPP issue?

  2. Don_K

    Aug 09, 2018 08:32

    When using with Unity 2018.1.8f1 and building an APK for Android with IL2CPP,
    There is still a similar problem in Galaxy Note 2 of Android 4.3.

  3. simonmeijer

    Mar 26, 2018 09:29

    This issue is bug is also present in Unity 2017.31f1 in the editor, iOS and Android devices.

  4. polytropoi

    Nov 11, 2017 17:46

    this bug breaks everything for me, when can we expect a release with a fix?

  5. zbarryte-luminopia

    Nov 09, 2017 22:31

    I'm also experiencing this issue. This issue is blocking my team from upgrading our product to use Unity 2017, which would give us great benefits in other areas; however, because of this issue, I cannot recommend Unity 2017 to the team.

  6. RichLogan

    Nov 08, 2017 10:46

    Interestingly, GetResponseHeaders also seems to return null on PC standalone builds when there is no response body (like when the request method is HEAD). Worked fine in 5.5.3, broken after upgrade to 2017.2.0f3.

  7. curi1119

    Oct 19, 2017 10:32

    This happens only when I builded on CloudBuild for Android.
    Not happens when I build on my PC.

  8. yurykorzun

    Oct 17, 2017 13:44

    In our case, having "Content-Encoding": "gzip" and "Content-Type":"octet-stream" in request headers resulted in no headers being returned.

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.