Hello, we’re the developer of the Responsive Google Maps plugin that has the conflict.
The conflict is caused by the plugin folder name, not the actual title.
Unfortunately, WordPress naively uses this folder name (and not a unique ID that they could place within each zip file on submission such as how Chrome Extensions have), and two plugins with the same name are effectively the same.
Our plugin is only on CodeCanyon, but 1.2.0 was detected as a greater version than ours, so our customers were receiving this as an update.
As a temporary stopgap, we released a version as V10, but we do not have an automatic update system.
Renaming the folder will make them independently recognized. Unfortunately, our uninstall process pre-V10 would clear all settings (including our custom posts), so if we changed our name and people installed that and removed the older plugin via WordPress, they would lose everything.
We planned to rename the folder initially, but this data loss and lack of autoupdate on our side was determined very likely to cause data loss. Our customers may be unaware of the update, as CodeCanyon is opt-in for release notifications, and there’s nothing within WordPress to let them know.
I don’t know if WordPress would allow pushing a version on your side with a renamed folder path or not, since they use it for version identification.
