Missing/outdates maps IMPEACHING route calculation.

[beatnickgr]

Description

When some maps are missing/outdates, the route is not calculated with what is available.

Steps to reproduce

Download maps of Greece, Bulgaria, Serbia. Do not download North Macedonia if your vehicle is not insured there.
Try a route from Larissa to Pirot.
It's a long route, so depending on your device it can take up to 10 minutes, according to the suggestion.

Actual result

After 10 minutes the route is not being calculated at all, you scroll down to find a "missing or outdated maps", tab details, tap to "use downloaded maps" and then wait again another 10 minutes.
When you're arrived in Pirot and want to drive back to Larissa, the issue will reappear, because the previous choice was NOT STORED.

Same issue appears when your map is outdated. But when you're driving, it's a very bad timing to update. We don't want to use our data pack, and we just want the route with the available map. We will download the update when we're no longer driving and on wifi.

Expected result

If start and end are in maps with common borders, start immediately the calculation of the route.
Show a suggestion to download the missing/outdated map of this month
If it is declined, do not suggest the specific update again.
Still show updates for other regions, and show this region's next update.

Your Environment (required)

WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!

OsmAnd Version: 4.9.10 (and the versions of past few months)

[yuriiurshuliak]

I attempted to reproduce the bug using the following steps:

1. Downloaded the maps of Greece, Bulgaria, and Serbia, but did not download North Macedonia.
2. Tried calculating the route from 39.6390245432354, 22.419119228706997 (Larissa, Greece) to 43.15705773092889, 22.583996952350283 (Pirot, Serbia).
3. A "missing or outdated maps" notification appeared immediately during calculation. After clicking on Details > Use downloaded maps, the route was successfully calculated in about 8 seconds.
4. For the return route, clicking the return route button started the calculation immediately, without the missing or outdated maps notification. The calculation took about 9 seconds.

Since we could not reproduce the issue as described, please try resetting your profile settings:
Menu > Settings > App profile (Driving) > Reset to default.

Additionally, we recommend testing with our nightly build:
🔗 Nightly Builds

OsmAnd~ 5.0.0#4400m, released: 2025-02-18

video_2025-02-18_17-52-54.mp4

[beatnickgr]

The time of calculation greatly depends on the device you're using. With an old smartphone, it's usual to wait minutes (not seconds) when the distance is above 200km.

Step 3, when you say the notification showed immediately, didn't you have to scroll to find it? I've tried 2 different OS (LineageOS, /e/OS) and with both I had to scroll (after I noticed the calculation is not happening).