Extension Rejected for “Unused storage Permission” — But Actively Using It

[Incarnae]

Hi everyone,

I’m running into an issue with my Chrome extension review process and I’m hoping someone here has experienced (and solved) something similar.

My latest update was declined because the reviewer/ automated review stated I wasn’t using the storage permission, and they requested that I remove it. However, the extension very clearly uses chrome.storage.local in multiple places.

To address the concern, I even added the following line to my background.js to make usage more explicit:

chrome.storage && chrome.storage.local && chrome.storage.local.set({ lastApiRequest: Date.now() }, () => {}); 

My assumption was that the initial rejection might have been triggered by an automated review that missed the actual usage locations, so I added this explicit call before resubmitting. It is still pending at the moment but this update is very urgent and need help from others if I may be doing something wrong.

Has anyone here run into this problem? How did you get your extension to legitimately use the permission despite it being presented in the code.

My extension serves 2,000+ active users, and the delay is negatively impacting them. Any guidance, tips, or examples would be greatly appreciated.

[Oliver Dunk]

Hi,

It looks like the reviewer may have included the wrong permission in the last email that was sent. There is an unused permission, but it is the `scripting` permission.

Could you try submitting with that permission removed or functionality in place which utilizes it?

Thanks,

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/ae1511e4-2fe9-4251-8042-7b0b747870adn%40chromium.org.

[Incarnae]

Hi Oliver,

Thanks for clarifying. Out of curiosity, how were you able to tell that the unused permission was scripting? I’m guessing that may have been the issue, so I’ve removed it as suggested.

Since this was a minor and possibly mistaken flag, do you have any idea when the updated extension might be published?

Thanks again for your help

[Oliver Dunk]

Hi,

I found this on our end, unfortunately looking at parts of the verdict that you wouldn't have access to.

However, as mentioned this seems like a mistake and in general you should always get an accurate indicator of the problem as part of your rejection email :)

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB