About installing WebExtension with an existing legacy extension

Hi All,
I had a legacy bootstrap add-on, and its id is, for example, foo@example.com in the install.rdf file. I converted it to WebExtension recently. According to this document:
I use the same id in the manifest application key:
“applications”: {
“gecko”: {
“id”: "foo@example.com",
“strict_min_version”: “48.0”
}
},
Everything is fine when signing and publishing the WebExtension on my AMO (distributed on my own).
My browser already has the legacy extension installed, After I download and install the latest WE, both the legacy and WE appears. I was expecting that with the same ID, the WE one should replace the legacy one.
Is this expected design? or is there another workaround?

Thank you very much:)

The new version should have replaced the old one. It sounds like the IDs are not the same. Did you upload the new version as an update for the old one, or did you try to create a new listing on AMO?

Hi Jorgev,
I upload the new version as the update for the old one in AMO.
And I checked just now, the issue is resolved, as you said, the new extension replaced the legacy one correctly. I may installed the wrong add-on before.
Thank you very much:)