OsmAnd live: POI data displayed

[scaidermern]

The map still shows the old POI name (Istrien Gourmet) while the POI info already shows the new name (Verde 22):
https://www.openstreetmap.org/node/9123988124

Map and POI info show a brewery although the brewery tags have been removed:
https://www.openstreetmap.org/way/316383846

Map Germany_bayern_europe.obf is from August. No overlapping maps activated. Deleting and redownloading live data doesn't help.

OsmAnd 4.5.10.

(This is actually the same report as #17893. However, in my case I can still reproduce this bug.)

[Nine-Tailed]

See #17887

[Citro12]

Problem is solved for me by deleting the base map of the respective federal state and downloading it again

[scaidermern]

Problem is solved for me by deleting the base map of the respective federal state and downloading it again

Didn't work for me. I already tried re-downloading Bavaria and live data, two times. The old data is still displayed.

[UserMicha]

Problem still alive with Version 4.5.10 from 9.8.23! New ways are shown together with old ones. I could solve this by switching back to rendering engine 1. Delete and new download of the complete map didn't help.
Compare OSM website with OsmAnd:

[DmitryAlexei]

@UserMicha try to clear the live updates cache. Sometimes opening and closing OsmAnd multiple times can help.

[UserMicha]

Unfortunately, that doesn't help. I also deleted the cache of the app in the Android settings and ended it hard. Map is rebuilt, but the same appearance. As before, only switching to Engine 1 helps. It is Android 10 on a Samsung XCover.

[vshcherb]

To be fixed with this issue - #14714, #17834

[vshcherb]

Tasks need to be retested (probably related to #18153)

[ivanPyrohivskyi]

I can not reproduce this bug and no idea what happen.
I think need to check order of map during rendering and check if request to retrieve POI information is no depended from rendering.

[ivanPyrohivskyi]

One idea yet.
Need to check order of map using in rendering.
As I can see from code for amenity after retrieve info from rendering layer we launch of finding amenity from map, so data on screen and POI info can be different.
Same issue I think with deleted amenity. Even with check on closed amenity we forgot that they are searching in all maps (base and live updates).

[vshcherb]

@ivanPyrohivskyi how will it fix road duplicates problem with code for amenity?
#18153

[ivanPyrohivskyi]

@ivanPyrohivskyi how will it fix road duplicates problem with code for amenity? #18153

On amenity example I explained that problem in rendering side and separate request to data from Java produce right info.

[vshcherb]

To do: try to reproduce the issue similar to (#14714 (comment)) - be aware it's not present with v1

[vshcherb]

@scaidermern are you able to reproduce it lately? We still can't catch the bug but if you can pinpoint to latest changes related to this #14714 (comment)

[Dimitar5555]

To do: try to reproduce the issue similar to (#14714 (comment)) - be aware it's not present with v1

I've been able to reproduce it at 42.50239 27.46734 (December 2023 map of Bulgaria with live updates, OsmAnd 4.5.10 on Android 10). The problem is present regardless of the rendering engine. To reproduce it, delete ways which are part of route relation.

[scaidermern]

@scaidermern are you able to reproduce it lately? We still can't catch the bug but if you can pinpoint to latest changes related to this #14714 (comment)

No, I can't reproduce it with OsmAnd 4.6.8. But I rarely update roads and I'm not sure under which exact circumstances the bug did occur. So maybe it is fixed, maybe it isn't.

[ivanPyrohivskyi]

I could not reproduce this bug. Previous request was wrong.