BLITZ.GG not working

[HannoMartinus]

As of 20/04, blitz.gg stopped working on version 1.15.0

Status Update (25/05/2022):
BLITZ.GG: Down ❌
Lolalytics: Down ❌
OP.GG: Down ❌
U.GG: Working ✅
METAsrc: Down ❌

[89Q12]

Hi, thanks for reporting this👍
Currently I can't look into it but I will fix it as soon as I have time again.
Does it happen on every champion or just Malzahar?
EDIT: From a quick look seems like they switched to graphql and here the endpoint we can use I guess:

Graphql endpoint

Formattes for better readability

https://league-champion-aggregate.iesdev.com/graphql?query=query 
ChampionBuilds($championId:Int!,
$queue:Queue!,
$role:Role,
$opponentChampionId:Int,
$key:ChampionBuildKey)
{
  championBuildStats(championId:$championId,
  queue:$queue,
  role:$role,
  opponentChampionId:$opponentChampionId,
  key:$key
  ){
      championId  opponentChampionId queue role builds{
      completedItems{
        games index  averageIndex itemId wins
      }
      games mythicId mythicAverageIndex primaryRune  runes{
        games index runeId wins treeId
        }skillOrders{
          games skillOrder  wins
        }startingItems{
          games startingItemIds wins
        }summonerSpells{
          games  summonerSpellIds wins
      }wins
    }
  }
}
&variables=
{
"championId":103,
"role":"MID",
"queue":"RANKED_SOLO_5X5",
"opponentChampionId":null,
"key":"PUBLIC"
}

[Soundofdarkness]

I personally have nearly no knowledge of graphql either, but im going to take a look if I have time too. (I will mention it here if im working on it so we don't end up with two people fixing the same)

[89Q12]

Arrgh well I allocated Monady and Tuesday next week of my time to fix all the plugins. I hope I get them all fixed in those 2 days

[89Q12]

@HannoMartinus Fixed blitzgg and opgg is already fixed just not released but if you want to try it out you can build from my fork or just wait until the new releas but I assume that will take a while since #118 is still present. Fixing that is time consuming

[Soundofdarkness]

Yup, going to take a look at the PR's soon, and I'm not sure, should we just try to revert the last PR for the time being and re-add it later on ? (at least in case we don't find any obvious cause soon). Or well, probably not latest but #116 and #117

[89Q12]

I have a better idea:
We make a dev branch from current master and rebase master onto 0edd00f and merge current PRs.
That way we can experiment with it and in the mean time release a new version so that the program is in a more useable state.
What do you think?

[Soundofdarkness]

Yup, sounds good, going to work on doing that tomorrow (since i think i have to do it, but not sure, or well, i will try to asap, just as last date tomorrow)

[89Q12]

Sure, or if big if you feel I can be trusted add me as a collaborator and I can do that. Wow I feel bad for bringing this up anyway thanks for your quick response time

[Soundofdarkness]

Don't worry, I will for now still see to that, but that is something I'm debating anyways if I'm continuing to not be able to do anything to help (as in, moving the project into a community, and giving 1-3 people trusted access as maintainers after a vote if they want and with me just being there in case I have time for once)
(And the vote just because I feel like I shouldn't decide on something like this alone, especially not when I'm not even doing much of the work anymore. )