Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connectivity issues #3

Open
meirtsvi opened this issue Aug 15, 2011 · 0 comments
Open

Connectivity issues #3

meirtsvi opened this issue Aug 15, 2011 · 0 comments

Comments

@meirtsvi
Copy link
Owner

While you drive you sometime receive "operation timed-out", "operation failed" or see the next tiles not being drawn.
This happens due to connectivity issues I wasn't able to pinpoint yet.
Another input is that when you close Waze and re-open it, the tiles or search for trip suddenly works ok.

On the emulator I encoutered several occasions where the tile URL suddenly stopped responding (giving 404) and few minutes later responded ok again. The error handling of web requests may be wrong when returning 404 from the C# code to the C code.

The C code should be investigated in order to find out how the web error handling is being done and change the C# code to send the appropriate error code to cause the C code to really retry the failed operations (I suspect it doesn't in the current version).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant