Closed WildEgo closed 5 years ago
It looks like something has been changed on the API. I'll investigate the issue and publish a fix.
It looks like something has been changed on the API. I'll investigate the issue and publish a fix.
really appreciate it man good job on the package, keep us updated
The issue should be resolved now. If you bump into it again open another issue and I'll have another look.
I believe the cause was that the Riot API's Shard status response object had changed. It now has a heading inside MessageDTO which was not documented on the Riot API site.
I have released the patch under the tag 1.3.1
.
Describe the bug I really don't have a good explanation the request is just not created I'd suppose
To Reproduce Steps to reproduce the behavior:
Expected behavior Should've returned anything that is not an error
Desktop (please complete the following information):
Additional context Should be manifest.json related