[BUG] Spectator V4 always returning 404 after patch 14.1

jlcarvalho commented 10 months ago

Bug Description
Spectator V4 always returning 404 after patch 14.1.

Problem Description
When we try to request infos about a player's match using the spectator v4 api, we always get 404 Data not found.

Expected Result
The API should return the expected match data.

Actual Result
Captura de Tela 2024-01-10 às 12 35 01

Developer Impact
Our App has some challenges based on the current match of the player, without this API we can't connect the match to the player in real time. Our app crashes when trying to finish the challenge, since there is no match connected.

Frequency: Every API call
Severity: My whole app is crashed right now.
Cost: The challenges are the main purpose of the app, so, without this we can't run anything.
Efficiency: Requires me to make 10x more API calls than necessary to compensate for the issue.
User emails: Every user is creating support tickets to report the bug.

Player Impact
Describe how this affects League of Legends players. Please include the frequency and severity of the issue.

Frequency: Every time a player tries to complete a challenge.
Severity: My whole app is crashed right now.
Quantity: There are 600 players that experienced this issue so far.
Region: This affects players in BR.

Issue Comments
Might want to leave this as instructions for any replies to your issue:

If you're also experiencing this issue please add any additional context that is useful, the developer impact to yourself, and the player impact to your users. As an example, if spectator-v4 isn't working it might affect a scouting site, but it could also affect a mobile app or site to share replays. Give the context on how this issue affects your project.

tisbells commented 10 months ago

Hey there - We're working on a resolution for Spectator issues and will provide an update as soon as we can.

uncgopher commented 10 months ago

This issue is also impacting twitch.tv/TrackingThePros - the stream is completely offline until fixed

tisbells commented 10 months ago

This should now be resolved, let us know if not

omarali commented 10 months ago

Spectator v4 active-games is working but spectator v4 featured-games is still broken

tisbells commented 10 months ago

Featured-games should be good to go now

jlcarvalho commented 10 months ago

Working as expected right now. Thanks.

uncgopher commented 10 months ago

Confirmed, thank you!

hackoh commented 10 months ago

@tisbells Active game data is fine now. But these game data cannot be spectated still. For example, http://spectator-consumer.na1.lol.pvp.net:80/observer-mode/rest/consumer/getGameMetaData/NA1/4889990749/0/token is returning 404 even this game is live.

uncgopher commented 10 months ago

About to dig into this more, but while the API endpoint is working and returning information, the command prompt that previously worked no longer does for launching spectator mode. Currently it launches a black screen but then nothing else happens; I also waited >5 minutes to make sure it wasn't the new spectator delay. Spectating works without issue when launching from the LOL client on the same PC.

Command prompt used (and I've tried multiple regions): cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator-consumer.euw1.lol.pvp.net:80 vGUEw+ZXk2ehfkVt52tCHmaNFSI/lFAb 6765375583 EUW1" "-UseRads"

mrdotb commented 10 months ago

I dig and I will save you some time. Here is the changes I found:

The spectator api featured is now working but now they add TFT game inside. (not mentioned on a doc maybe a mistake)
```
"gameMode": "TFT"
```

The observer api changed subdomain.

# "http://spectator-consumer.#{platform_id}.lol.pvp.net:80" => before
"http://spectator.#{platform_id}.lol.pvp.net:8080"

hackoh commented 10 months ago

use spectator spectator.euw1.lol.pvp.net:8080 instead spectator spectator-consumer.euw1.lol.pvp.net:80 but it takes a min for loading or timeout on my client. any solutions?

uncgopher commented 10 months ago

Changing to cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator.euw1.lol.pvp.net:8080 q4cbbB1u+Sc99+A6sDyCIJmp6rHiHMn6 6765379443 EUW1" "-UseRads"

Resulted in the game loading screen with players/champions being shown, but then I got an error saying spectator info could not be downloaded. Note that I changed the URL to "spectator.euw1" from "spectator-consumer" and updated the port to 8080.

Also, your comment about the TFT mode and then "gameMode": "TFT" - is that supposed to be handled somewhere in the call (to specify that it's only for LOL)?

uncgopher commented 10 months ago

Confirmed the URL is the right one after capturing traffic when launching spectator from the client

uncgopher commented 10 months ago

I was able to get a KR game to load: cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator.kr.lol.pvp.net:8080 Hu9fWjgjaWSMZrknHXhBkc5BCEkzv611 6900641378 KR" "-UseRads"

It worked and with minimal loading time. However, an EUW game did not (Unable to download spectator data. The game will now exit): cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator.euw1.lol.pvp.net:8080 GnXeOypzw92Plfg87I7Z3I6VO33zWwzE 6765448344 EUW1" "-UseRads"

For BR, it also failed, same as EUW: cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator.br1.lol.pvp.net:8080 Mlh9SaJ8LpQgUTIKNUA3JdW4rZkVF1bV 2872698032 BR1" "-UseRads"

For NA, it failed: cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator.na1.lol.pvp.net:8080 av+cn9ZkaY1DU613ml8PIyCknMpMsbdZ 4890472413 NA1" "-UseRads"

So potentially a server region issue?

However, when I tried another KR game it also failed: cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator.kr.lol.pvp.net:8080 kU77a6XMEX4KKvIDyBbfoNK28JCer6a7 6900667660 KR" "-UseRads"

uncgopher commented 10 months ago

And then trying the same KR game (last one listed above) then worked, so maybe an intermittent issue? Or potentially the game needs to have been playing longer, but that game was at least 5 minutes into it, and trying another game that's listed at 24 minutes currently fails too.

Then immediately after typing out the above, I was able to load a game that was only 4 minutes in: cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator.kr.lol.pvp.net:8080 XNJhOCwQ/QQUE0ZaqhS0MS2QOY4bhOhI 6900691272 KR" "-UseRads"

hackoh commented 10 months ago

Observers still look unstable. They are affecting even spectating via client.

andres66c commented 9 months ago

This issue is also impacting twitch.tv/TrackingThePros - the stream is completely offline until fixed

very true, although on YouTube there are channels like "lol korean pro replays", "Challenger replays", etc., that are uploading repetitions of this patch, apparently they managed to solve it!

bangingheads commented 9 months ago

This issue is also impacting twitch.tv/TrackingThePros - the stream is completely offline until fixed

very true, although on YouTube there are channels like "lol korean pro replays", "Challenger replays", etc., that are uploading repetitions of this patch, apparently they managed to solve it!

Replays are completely different than live spectating

corysimmons commented 9 months ago

If there are still problems with this can someone open up a new issue so Riot devs can put eyes on it?

uncgopher commented 9 months ago

Seems like things have stabilized - I haven't been getting that error any longer and the stream has been running without issue.

RiotGames / developer-relations

[BUG] Spectator V4 always returning 404 after patch 14.1 #876