Steps to reproduce this issue:
None of these addresses appear in the app. I deleted and re-added them, but it still didn’t work. Two of the addresses are the same. Only one is in HN format, and the other is the RPP version of the same address. The third address is an old address belonging to the same location, but in RPP format.
Moreover, even the street name to which the HN address belongs is still not found in the app’s search. The user who owns the address is unhappy with the situation.
Furthermore, only the third old address appears in WME’s own search. The other two cannot be found even in WME’s own search.
Thank you for reporting this problem! I was able to reproduce it on my end as well. I have filed an internal ticket, and the team has started investigating this high-priority bug.
I will keep you informed on any further updates in the comments here.
Hope you’re well.
I’d like to let you know that the issue has been fixed on our end, Could you please verify if the affected addresses are searchable now for you?
I was just planning to share an update on this topic today. You read my mind!
Actually, we can say the issue is largely solved. Because user satisfaction is what matters, and now both addresses appear when searching on the application. However, for some reason, one of the addresses still doesn’t appear in the editor’s own search engine, unlike the other .
Thanks a lot for your response!
As for 68A Lütfəli Abdullayev, it is indeed not showing up in the WME search results. I’m checking upon this issue with the team. Please let me know if you come across any other cases where addresses are not shown in the WME search drop-down.
I did a bit more testing focusing on extended HN and RPP formats and noticed that such addresses are not returned in the WME search drop-down. If you spot more examples yourself, please let me know.
Meanwhile I’ve filed an internal ticket to look into this.
Yes, you’re right, there are multiple similar cases, and we definitely need to check to find out which other addresses are affected. Or else it seems incomprehensible. It seems the problem is more than just a localized issue involving a single address. Two additional different samples:
Thank you for the examples @Max_Booster!
Just to make sure this bug is tracked correctly, if you could open a separate ticket in Production Bugs, it would be much appreciated.
.