Many users have reported that they are getting Unknown Error -13 or -5 in League of Legends: Wild Rift. As a result of which, they are even unable to load the game in the first place. This issue first came to light after the update v3,2 which made some substantial backend changes, including checking out the source from where you have downloaded the game. If it has been downloaded from any other location apart from Play Store, then it will straightaway prevent you from accessing the game. But why would anyone sideload the game from a third-party site?
Well, this is because some devices don’t come with Google Mobile Services. As a result, they don’t have any Google Apps, Services, and Framework, including the Play Store. So their only course of action is to sideload apps from third-party apps/sites. And all the users who had taken this route to install League of Legends: Wild Rift are currently getting either Unknown Error -13 or -5. If you are also in the same boat, then this guide will make you aware of a nifty workaround to resolve this bug. Follow along.
How to Fix League of Legends: Wild Rift Unknown Error -13 or -5
To resolve this issue, you will first have to remove the signed-in account from your device. After that, delete the data of Play Store and Services. Then connect your device to the US or Singapore server via VPN and create a new Google Account. Then keeping the VPN enabled, you should now be able to download and install the game directly from the Play Store without any issues. So let’s put this fix to the test right away. That’s it. These were the steps to fix the League of Legends: Wild Rift Unknown Error -13 or -5. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.
Cannot log in to League of Legends on Mac: How to FixHow to Fix Apex Legends High CPU Usage after Genesis Update