Game crashes everytime EOS response happen to produce result_code:19 (EOS_OperationWillRetry)

[ElekKartofelek]

Usually everything works okay as long as the response code isn't failing and retrying.
When that happens everyting closes on second retry with no error 🥴

SDK LogEOSSessions | The Social Overlay will not know about this session (Test Session 3).
SDK LogHttp | 00000163A89A1A00: request has been successfully processed. URL: https://api.epicgames.dev/matchmaking/v1/5a02dfc68ce64e2abb28581c2e4b212a/sessions, HTTP code: 503, content length: 75, actual payload size: 75, elapsed: 4.21s
SDK LogHttp | 00000163A89A1A00 Response Header Date: Wed, 22 Jan 2025 11:19:04 GMT
SDK LogHttp | 00000163A89A1A00 Response Header Content-Type: application/json
SDK LogHttp | 00000163A89A1A00 Response Header Content-Length: 75
SDK LogHttp | 00000163A89A1A00 Response Header Connection: keep-alive
SDK LogHttp | 00000163A89A1A00 Response Header X-Epic-Correlation-Id: EOS-cFwUOlWV30qbpD8a1tDWXQ-mxE1je8730OcrJnGNvq54A
SDK LogHttp | 00000163A89A1A00 Response Header X-Epic-Error-Name: errors.com.epicgames.common.ask_timed_out
SDK LogHttp | 00000163A89A1A00 Response Header Server: eos-gateway
SDK LogHttp | Lockout of 2.082400s on https://api.epicgames.dev/matchmaking/v1/5a02dfc68ce64e2abb28581c2e4b212a/sessions
--- Sessions: update_session: { "result_code": 19, "client_data": , "session_name": "Test Session 3", "session_id": "" }
SDK LogHttp | Retry 1 on https://api.epicgames.dev/matchmaking/v1/5a02dfc68ce64e2abb28581c2e4b212a/sessions
SDK LogHttp | 00000163A89A1A00: request has been successfully processed. URL: https://api.epicgames.dev/matchmaking/v1/5a02dfc68ce64e2abb28581c2e4b212a/sessions, HTTP code: 503, content length: 75, actual payload size: 75, elapsed: 4.20s
SDK LogHttp | 00000163A89A1A00 Response Header Date: Wed, 22 Jan 2025 11:19:10 GMT
SDK LogHttp | 00000163A89A1A00 Response Header Content-Type: application/json
SDK LogHttp | 00000163A89A1A00 Response Header Content-Length: 75
SDK LogHttp | 00000163A89A1A00 Response Header Connection: keep-alive
SDK LogHttp | 00000163A89A1A00 Response Header X-Epic-Correlation-Id: EOS-cFwUOlWV30qbpD8a1tDWXQ-mxE1je8730OcrJnGNvq54A
SDK LogHttp | 00000163A89A1A00 Response Header X-Epic-Error-Name: errors.com.epicgames.common.ask_timed_out
SDK LogHttp | 00000163A89A1A00 Response Header Server: eos-gateway
SDK LogHttp | Lockout of 6.589923s on https://api.epicgames.dev/matchmaking/v1/5a02dfc68ce64e2abb28581c2e4b212a/sessions
--- Debugging process stopped ---`

I fully acknowledge the fact connection failing is an issue on EOS side but I don't think ANY error response from Epic servers should result in my game crashing all together.

I am certain EOS is the only reason of the crash. I set up 3 types of networks and following does not occur neither on Steam nor LAN network. I haven't found a way to stop it from retrying either so essentially if result_code 19 happens you already know it's going to crash and there's nothing you can do about it.

Exported game closes with following console print but I doubt if will be helpful:

[3ddelano]

How to reproduce this issue?

[ElekKartofelek]

That's the catch. I'm afraid it can't be reproduced reliably as it's impossible to force response code 19 from Epics servers. It happened only today for 2 hours or so and I've never encountered it before nor had any issues with other error codes.

[3ddelano]

Oh that sucks. Anyways let me research a bit more about it