Diablo 4: PS5 and Xbox game Ultimate Edition early access release ...

Gaming

The issue is dogging console users, who have been unable to enjoy their early access periods

That's all well and good of course - standard practise in today's video game business landscape - but at the time of writing, there have been multiple reports from console that they're being met with a fairly common error that reads "Unable to find a valid license for Diablo IV (Code 315306)".

These reports are coming from people who legitimately bought a valid version of the game - and paid extra for the chance to gain early access - which indicates a problem between the PlayStation and Xbox platforms and Blizzard's servers.

The issue seems to be more widespread on PS5 - Xbox users appear to be more satisfied with Microsoft - but reports have been coming in from both sides.

Has Blizzard acknowledged the problem?

Blizzard has acknowledged the problem in this forum post and through its community manager, though it hasn't really offered any solution to the problem beyond "the team is looking into this."

"We are seeing reports regarding PlayStation users experiencing Invalid License errors," says the post. "The team is looking into this right now and will update once we have more information."

A further post adds that Blizzard and its partners have "done some work to help mitigate this issue," but the team is still asking for players to provide "as much detail as possible" when reporting the issue "as we continue to work on this with our partners."

How can I fix the problem?

At the time of writing, there does not seem to be a fix for the issue.

Some have suggested reinstalling the 80GB game and similar drastic moves, but this is unlikely to solve the issue, which appears to be some sort of conflict between the PlayStation and Xbox platforms and Blizzard's servers. But you can take a little assurance in the fact the issue is widespread, so you are not alone.

Some Diablo players have expressed worry at another possible instance of "Error 37", the old error code that perpetually stymied Diablo III at launch in 2012. That infamous issue was caused by overwhelming demand and a high volume of players attempting to log in simultaneously.

Many players were unable to play the game for several hours or even days after its launch, and the error prevented them from progressing in the game or accessing its online features. It seems unlikely that we're seeing anything that bad this time around, since this is a console-specific issue, which suggests Blizzard's servers are not completely collapsing as a whole.