Fix for no coordinates from Google API in some gamemodes or locations #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've also faced that issue, but only when I was playing no move in some locations. I figured out that the problem was about the
XMLHttpRequest.prototype.open
function, because for some locations it worked properly, and for some locations it wasn't called at all. I went through some problematic locations again but with DevTools Network tab opened, and found that not onlyGetMetadata
Google API's endpoint is used, but sometimes alsoSingleImageSearch
, that provides exact or similar information toGetMetadata
. So I addedSingleImageSearch
endpoint as well, and tested it for a while, and it seems like adding it fixes the issue.I've also added a check for the method to be a
POST
, because requests to these endpoints are preceded byOPTIONS
requests, that don't contain any useful information for parsing coordinates.