overwolf.replays.onCaptureError: StreamingErrorEvent: "failed to start game recording" on Lol match end

This is an error that some of our users receive (about 1k a week).
when playing lol, and no highlight was captured, on match end the replays onCaptureError throws the following error:

{"error":"StreamingErrorEvent","reason":"failed to start game recording","additionalInfo":"Unknown"}

We were unable to reproduce the issue consistently so we don’t know to pin point at what scenario does it happen

Impact for my app: mid
Do you currently have a workaround? No, this is purely a replays API issue

User Logs:
ow_4b533e32-1a4c-49b4-8df0-ad652b612524-2020-07-09-08-45-46.zip (1.6 MB) ow_241a06c0-7b4a-4b98-be0b-e0dcdd829321-2020-07-09-19-15-37.zip (1.2 MB)

times of errors:

ow_4b533e32-1a4c-49b4-8df0-ad652b612524: 2020-07-08 20:38:25,688
ow_241a06c0-7b4a-4b98-be0b-e0dcdd829321: 2020-07-08 17:36:33,892

@shir.brass to clarify and understand the issue: before i deep dive to the logs - did you get all the events as expected, etc., and you just got the unwanted StreamingErrorEvent error, OR you were supposed to capture the highlights, and they weren’t captured at all?

Hi. We examined the logs, and we found out that this is a PBE client, which is not supported.
Besides, the PBE allows you to run LoL in DirectX 11, which not supports highlights recording yet.

BTW - you mentioned that it happens to ~1K users per week. Note that this is a friction of your users (~0.05 or something like that from your users, I don’t remember the exact number). So basically, a minority of your users get that error.

so, assuming that the issue is PBE, how can I determine that my session is PBE & not a regular LoL run?
is there a flag marking it?

otherwise, these users will keep getting this error…

@shir.brass You can use the summoner_info: when it’s a PBE client, it returns PBE instead of the region:

{"feature":"summoner_info","category":"summoner_info","key":"region","value":"PBE"}.

I added it to the documentation.

In addition, you can check the command line using getRunningLaunchersInfo() or getRunningGameInfo().

1 Like

we’ll handle PBE from our end (say that it’s not supported), and let’s see if this issue still reproduces afterwards :slight_smile:
thanks for the quick reply :pray: