question

zymakenneth avatar image
zymakenneth asked

[Unity 2017] Fatal Error on Android - Get response Headers

I am running into problems with a fatal exception with the following setup:

Unity 2017.2.0f3

Playfab SDK 2.23.171106 and latest editor extension

Android API level 24

Not sure if something changed with Unity's Get response Headers. However, hard crash on Android build attempting to simply call Login with google account. I have not found a workaround (disabled Playfab for the time being).

I am also seeing the login request on my playfab dashboard and an error for "invalid params". I double checked that I am sending the server auth code and title ID.

E/CRASH ( 3406): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000 E/CRASH ( 3406): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** E/CRASH ( 3406): Build fingerprint: 'samsung/gtexswifixx/gtexswifi:5.1.1/LMY47V/T280XXU0AQA4:user/release-keys' E/CRASH ( 3406): Revision: '5' E/CRASH ( 3406): pid: 3406, tid: 3423, name: UnityMain >>> com.Zyma.AlphaBuild <<< E/CRASH ( 3406): r0 00000000 r1 910950a0 r2 8706a210 r3 00000000 E/CRASH ( 3406): r4 a06d9c10 r5 a16d691c r6 00000000 r7 8706dcf0 E/CRASH ( 3406): r8 00000000 r9 00000226 sl 00000002 fp a16d6528 E/CRASH ( 3406): ip a16d6478 sp a16d6528 lr af45db2c pc 9d6b5888 cpsr 34594d4c E/CRASH ( 3406): E/CRASH ( 3406): backtrace: E/CRASH ( 3406): #00 pc 00005888 ( UnityEngine.WWW:get_responseHeaders () + 0xf0 (0x9d6b5798 0x9d6b58a0) [0xaf46fee0 - Unity Root Domain]+22664) E/CRASH ( 3406): #01 pc 00002b28 ( string:CharCopy (char*,char*,int) + 0x90 (0xaf45da98 0xaf45db34) [0xaf46fee0 - Unity Root Domain]+11048)

...there is another post regarding a similar error after Unity changed the Get Response Headers in Unity 5. However, the post was closed and should have been resolved for newer Playfab versions.

10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

3 Answers

·
1807605288 avatar image
1807605288 answered

https://api.playfab.com/releaseNotes#180129

The latest UnitySDK finally has a workaround that completely bypasses the broken Unity response headers.

10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

zymakenneth avatar image
zymakenneth answered

Workaround is to use http instead of Unity www for the time being. I am not sure what the pro's and con's are of each approach to be honest (difficult finding any documentation on this).

10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Ian Oliver avatar image
Ian Oliver answered

I encountered a similar problem with 2017.1.2p1 (I think).

Moving to a newer Unity patch release fixed the problem for me.

I would suggest that you try 2017.2.0p2.

1 comment
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

zymakenneth avatar image zymakenneth commented ·

Thank you, I will toss this over to Unity and see if they can resolve if I find this works in another Unity version. I am using 2017.2.0f3 which is the leading official build so this is an issue that should be resolved.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.