Chrome Extension store reviewers rejecting extensions with react-player #1787
Replies: 6 comments
-
@animber0 https://github.com/transcrobes/transcrobes/blob/main/frontend/manifest.config.ts worked and was accepted at previous points. I ended up internalising the code because I only needed a fraction of it, the project is basically finished and the store was rejecting. |
Beta Was this translation helpful? Give feedback.
-
@animber0 no idea, sorry, and things seem pretty slow here, so you might want to investigate forking for your own requirements. |
Beta Was this translation helpful? Give feedback.
-
Hey @animber0 , I'm running into the same issue Did you managed to fix it? |
Beta Was this translation helpful? Give feedback.
-
Current Behavior
Store reviewers are rejecting extensions with
react-player
as a dependencyExpected Behavior
Store reviewers not to reject
react-player
as a dependencySteps to Reproduce
Environment
Other Information
In exchanges with the reviewer it appears that the "remote code" that causes the rejection are the links to the SDKs. That code is not executed - they just saw code that could be executed, and rejected. As my use of
react-player
is with a file and a custom player, I was able to get around the issue largely by copying the relevant code and removing all the SDK-based stuff.It may also simply be an overzealous reviewer rather than a change in policy - I have had several submissions succeed so I don't know whether this is the new normal or not.
I understand this might be a direct wontfix but it might be useful to have this here if others get a rejection and can't work out why!
Beta Was this translation helpful? Give feedback.
All reactions