BlockedException When Using Navitia API for Journey Planning

[Funnyklown]

Describe the bug
When attempting to plan a journey using the Navitia API through transportr, the app throws a BlockedException error. This issue occurs consistently with requests to Navitia's journey planning endpoint..

Error

de.schildbach.pte.exception.BlockedException: https://api.navitia.io/v1/coverage/fr-se/journeys?from=6.016762%3B43.109231&to=stop_area%3AOMT%3ANavitia%3ASISVEE&datetime=20241107T163610&datetime_represents=departure&min_nb_journeys=6&depth=0&walking_speed=1.344
de.schildbach.pte.util.HttpClient.getInputStream(HttpClient.java:294)
de.schildbach.pte.util.HttpClient.get(HttpClient.java:215)
de.schildbach.pte.util.HttpClient.get(HttpClient.java:208)

To Reproduce
Steps to reproduce the behavior (location is arbitrary but it can be anything else)

1. Open the transportr app.
2. Set the origin coordinates to 6.016762, 43.109231.
3. Set the destination to stop_area:OMT:Navitia:SISVEE.
4. Choose a departure datetime (e.g., 20241107T163610).
5. Attempt to retrieve journeys.

Expected behavior
The app should return a list of journey options between the specified origin and destination.

Versions:

• Transportr Version: 2.2.1
• Device: Samsung S21
• Android Version: 14

[Altonss]

Can reproduce, this is likely related to the shutdown of Navitia... see #907 (comment) .
Sadly it looks like we will have to remove Navitia providers very soon, and ideally update Transportr. A good replacement solution for those affected networks could be #954, but it is only an idea for now (no implementation).

Thanks for the report!

[Altonss]

I'll keep this issue open, until the next release is published :)