You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: