Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

Map download failed. Trying again. #11

Closed
ritolika opened this issue Jul 26, 2016 · 12 comments
Closed

Map download failed. Trying again. #11

ritolika opened this issue Jul 26, 2016 · 12 comments
Labels

Comments

@ritolika
Copy link

ritolika commented Jul 26, 2016

Can't get it to work, I've put in the api key and installed the req but it doesn't work.

https://i.gyazo.com/ffaee6bb4d636665da1b098700a77208.png

https://i.gyazo.com/f1ba1ca73ead3bc0e18afc74f040bf3b.png

@TraumFabriK79
Copy link

remove -c at the end of the command, it works for me that way

@nborrmann nborrmann added the bug label Jul 26, 2016
@ritolika
Copy link
Author

@TraumFabriK79 isn't that the thing that makes it faster?

@nborrmann
Copy link
Collaborator

It's a very weird bug. The niantic server refuses the connection when using pycurl until it times out.

It happens for some of my machines on some networks. (It doesn't work with my home network, but it does in my university). I suspect it has something do with SSL/TSL quirks.

There's no problem without the -c flag.

@ritolika
Copy link
Author

@nborrmann So if I try on another network there's a slight possibility that it might work?

@nborrmann
Copy link
Collaborator

Different OS, different network, etc.

I don't know what causes it.

@pudding889
Copy link

Also having the same issue here with -c producing map download failed errors.

@jimdrie
Copy link

jimdrie commented Jul 26, 2016

I had the same issue when using a Google account, -c failed. Using a PTC account afterwards worked fine with -c.

@nborrmann
Copy link
Collaborator

@jimdrie Wow, this is getting weirder by the minute.

@jimdrie
Copy link

jimdrie commented Jul 26, 2016

@nborrmann Not sure if that's what caused it, though, but that was my observation.

@nborrmann
Copy link
Collaborator

@jimdrie Is that behaviour reproducible? What happens if you switch back to a Google account?

@nborrmann
Copy link
Collaborator

Alright I fixed it.

The issue was with the DNS lookup. It sometimes takes ages which caused it to timeout. I pointed at the Google DNS server now, which fixes this.

@jimdrie
Copy link

jimdrie commented Jul 26, 2016

@nborrmann Nice. It was reproducible here: http://imgur.com/eZqSZhd

x0131349a pushed a commit to x0131349a/pogom that referenced this issue Sep 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants