Saving Error: "Invalid brand name" when selecting a Parking Operator

[Niccolo778]

Is this a…:
Standard bug
Steps to reproduce this issue:
It works great on some locations, but after adding it to a few, it suddenly freezes/glitches and shows this error (as shown in the attached photo). However, if I refresh the page or wait a little while, I can add it again without any problems. Note that this operator has been recently added.

Environment where the bug occurs…:
ROW
Permalink:
https://waze.com/ka/editor?env=row&lat=41.98627&lon=44.11280&zoomLevel=19&venues=28901796.289083495.41940768
Browser name and version:
Microsoft Edge Version 154.0.4258.48 (Official build) (64-bit)
Are you using scripts? Please detail which ones.:
No

[Olesya-Staff]

Hi @Niccolo778,

Thank you for your report.
May I try adding this operator as well?
To confirm, the correct entry is გორის პარკინგი, right?

Best,
Olesya

[Niccolo778]

Hi @Olesya-Staff

Yes, exactly! The correct entry is „გორის პარკინგი“

[Olesya-Staff]

@Niccolo778

გორის პარკინგი

Hi @Niccolo778,

I’ve just tried and the change was saved with no errors on my side.

[Niccolo778]

How many locations did you try to add it to? If you tried just one and it was added successfully, I do that too. I’m talking about adding to several places one after another, like adding one, saving it, and then adding to another location and saving. Try adding it to a few missing parking spots in the city of Gori, and it will give you an error on one of them.

[Olesya-Staff]

@Niccolo778

How many locations did you try to add it to?

Just the one you linked.

@Niccolo778

If you tried just one and it was added successfully, I do that too. I’m talking about adding to several places one after another, like adding one, saving it, and then adding to another location and saving. Try adding it to a few missing parking spots in the city of Gori, and it will give you an error on one of them.

I see, thank you for elaborating on this. I’ll try to reproduce in the test environment and will keep you posted.

Best,
Olesya

[Olesya-Staff]

@Niccolo778,

In the meantime, it would be helpful if you could take a screenshot of the console error when you encounter it again, such as:

[Niccolo778]

If it helps, I’ll send you a video of how it shows the error, and after a refresh, the same action works

[Olesya-Staff]

@Niccolo778

If it helps, I’ll send you a video of how it shows the error, and after a refresh, the same action works

Thanks a lot for the video, @Niccolo778! I have added it to the internal ticket and will let you know once there is an update.

Best,
Olesya

[Olesya-Staff]

@Olesya-Staff

Thanks a lot for the video, @Niccolo778! I have added it to the internal ticket and will let you know once there is an update.

P.S. I also managed to reproduce the error.

[Olesya-Staff]

Hi @Niccolo778,

I hope you are well.
I have just tried to reproduce the issue and did not get the error. Can you please check on your end as well?

Thank you,
Olesya

[Niccolo778]

Hello @Olesya-Staff
I just checked at a few different locations and it works well without giving any errors
Thank you.

[Olesya-Staff]

@Niccolo778

I just checked at a few different locations and it works well without giving any errors

Thank you for your response, @Niccolo778. I’ll go ahead and mark this bug as unable to reproduce, but let’s keep an eye on it when there is a new brand added.
I’ve asked the team whether the brand’s age could have anything to do with the error, and will let you know once I hear back.

All the best,
Olesya