Chrome extension v3 version upload problem

sangsoo

Member
Hello.
I am creating a chrome extension that selects a browser tab and publishes a stream to the startup API.
I am using flashphoner-room-api.js and it works well in the local environment using RoomApi.sdk.
When uploading the code to extension-store, it is rejected because there are encrypted codes such as 0xff in the js above.
I tried using cdn, but v3 also limits this method.

Is there a solution to the above problem or a guide for the v3 version of the Chrome extension?
Please reply. Thank you.
 

Max

Administrator
Staff member
Good day.
When uploading the code to extension-store, it is rejected because there are encrypted codes such as 0xff in the js above.
Please clarify the reason to reject.
Web SDK uses hex codes to support WSPlayer and MSE technologies, in both cases to decrypt a media data received via websocket to play them. The technologies are useless in RoomApi case (and WSPlayer is obsoleted), so we raised the ticket WCS-4320 to build WebRTC only RoomApi bundle. May be this will be enough.
 

sangsoo

Member
Thank you for your reply.
----------------------------------------------
Code readability requirements

Violation Reference ID: Red Titanium
violation:
The package contains obfuscated code (
Violating content:
Code snippet: lib/flashphoner/flashphoner-room-api.js: this[_0x162a("0x5")] = _0x566b31[_0x162a("0x5")];......
).
How to correct: Replace the obfuscated code with human-readable code and resubmit the entry.
Relevant sections of the Program Policy:
Developers must not obfuscate code or hide the functionality of their extensions.
------------------------------------------------------------------------------------------------
The above part is why it was rejected.

I also switched from using flashphoner-room-api.js to using flashphoner-webrtc-only.js.
Thanks.
 
Top