-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Navitia: BlockedException when searching directions #583
Comments
can't reproduce this here with the paris provider |
It was working as a charm until the upgrade.
On February 7, 2019 6:02:49 PM GMT+01:00, Torsten Grote <notifications@github.com> wrote:
can't reproduce this here with the paris provider
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#583 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ATuvAP11HIrKVfTvVzyyLcGzlryTbwdrks5vLFw5gaJpZM4ansZJ>.
|
This is strange...
I tried this morning for a trip in Paris and it's working.
Then i tried again for the same trip than yesterday that was in Paris suburb and then i got again the error.
On February 7, 2019 6:02:49 PM GMT+01:00, Torsten Grote <notifications@github.com> wrote:
can't reproduce this here with the paris provider
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#583 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ATuvAP11HIrKVfTvVzyyLcGzlryTbwdrks5vLFw5gaJpZM4ansZJ>.
|
Same issue for me since the update.
|
Does it happen on all searches? Also departures and nearby stations? Also non-saved direction searches? |
It seems to bug when it involves saved (starred) directions. Using history is ok for the few tries I've made. |
Strange. Might be similar to #207. I have no time to investigate this. Maybe somebody with a bit of technical knowledge can do this. |
In my case history is only working for Paris but not the suburb or if suburb involved.
On February 19, 2019 4:44:48 PM GMT+01:00, jeanrjc <notifications@github.com> wrote:
It seems to bug when it involves saved (starred) directions. Using history is ok for the few tries I've made.
I can't really try all combinations, so I can't say which one works for sure. But directions I saved are not working, but if I set the same locations by hand and if don't chose the saved locations that are proposed, it works.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#583 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ATuvABdBIE_cnAVU89fjOhpvxOLgJe90ks5vPBvwgaJpZM4ansZJ>.
|
@jeanrjc Where did you get this error from? This url lacks the coverage part, which causes the So there are really two separate issues here:
|
It's the exception I copied from the app, as in the screenshot above. |
@grote While investigating, I noticed Adding the coverage part would at least prevent this strange error and instead result in a (slightly better understandable) "invalid ID" error for the user. |
I'd say it should use the coverage in its requests, but I didn't write this provider, so I am not the authority here. How is this even working without specifying the coverage? |
This issue is fixed upstream. |
[
The text was updated successfully, but these errors were encountered: