… is an “installation specific id”, and not my “general” extension-id.
Good call, I honestly am not sure either.
But I cannot really test it without uploading to AMO
I see, it’s the chicken and egg situation. My suggestion if you plan on making use of that information is to add some sort of line or debug method (it would do nothing at all) just to check if that id is correct in a future version update you upload and go from there. After you confirm that you will know if you can use that id for anything after that.
Is this valid? I have no “applications” property in my manifest file!? I’m thinking it should be getManifest().browser_specific_settings.gecko.id , but it is probably easier to just use browser.runtime.id instead.
Sorry, seems like in MV3 “browser_specific_settings” replaced by “applications”.
telling it is mandatory to specify “your” id in manifest v3 before upload to AMO.
If you add your own id it would make things easier for sure, and that id would be returned by browser.runtime.id
as is too.
it is a good idea to insert the same id in manifest v3 as was used for MV2
Very good question, I honestly do not know how it works in your case since you never had your own id before, but AMO was adding one in place. I’m afraid I won’t be able to help you with that one thought.
I know this, in my extension additional details (where you can add featured screenshots and change the listing details) this information is shown:
I wonder what shows in yours, and if you can set yours. I cannot change mine because I always had it, but I wonder if someone who didn’t have before can add it there.