-
-
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
No connections found: Handle changes of location IDs #207
Comments
Do you still have the same problem? |
Yes, I'm on holiday and I come back home the day after tomorrow. I'll explain the problem better then |
Could you confirm that the latest version of the beta app is still 1.1.3? If I choose the first one, this error is shown: If I choose the second one, all goes well. Could you check if it is a problem of Navitia APIs, so that I close this bug and open another one in Navitia's forum? Thank you very much! |
My theory is that the Italy provider changed its location IDs, so when you search it finds the old one Transportr saved as a favorite and the new one. If you use the old one with the wrong ID, you get the error. I would need to investigate more to confirm this theory. You could help by checking |
I'd like to help you. Would you be so kind to tell me what to do? I don't know what |
Some quick pointers:
|
I finally succeeded in using logcat. Here is the output. I hope this helps! |
Thanks! That's a good start. I only found this once here:
It would be interesting to know how this changes with the second Dateo that works. If you could just post these two lines here, that would help. |
|
Thanks, so Dateo was |
If you want to know why they changed IDs to stops and how handle future changes, you can send an email to info@amat-mi.it (I can help you in translating it into Italian). |
Deleting old favorites is not possible at the moment, because normally(!!!) they don't change. Before talking to amat, I think we should talk to Navitia, because it might have been their fault the IDs changed. |
Are you going to ask Navitia about ID changing or should I do that? |
Meanwhile, I talked with Navitia two times in IRC. There's no real solution so far and probably none coming soon. We should at least try to show a meaningful error message and a way to recover from that error. In the API response, there should be a 404 error with an ID Someone would need to investigate the exact API response behavior and then return a proper error code from the |
According to PTE upstream, the issue is generally an unsolved problem: https://groups.google.com/d/msg/public-transport-enabler-discuss/eZK5MdDEDBE/d6rFSe6_AAAJ |
@dennisguse the code has now somewhat settled, so that you could think about implementing this. I suggest to discuss the general approach here though before starting to write actual code. |
@grote Sounds good! I will try to take a look after Xmas! |
@grote Do you remember what was the idea to implement at this point? As this is a general problem and happens in various providers it would be nice to at least be able to somehow cope with this without clearing the entire app data. |
I think the rough idea was to see if we get reliable info to determine that an ID is no longer valid, then either delete everything saved with that ID, so that people can re-add things with the proper ID or try to find the new Id and replace the old one. |
An error is shown when looking for some stations, e.g.
Dateo, Milano
andGaribaldi Fs, Milano
. I don't know if it is a Navitia problem or Transport problem, so I start reporting the bug here ;)The text was updated successfully, but these errors were encountered: