Src: Can't load extracted folder as extension

[Cyberavater]

As a result the .zip is extracted in the cache and gets deleted randomly after some time.
https://github.com/Sainan/Universal-Bypass/issues/1387

Possible workaround; Having an option (enabling) which extracts and loads the extension from a permanent folder (a non-cache folder of the app).

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.71. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[Delphox]

A workaround to avoid the cache deletion issue is packaging the extension folder into a CRX via the Pack Extension option and then installing the resulting CRX (putting the full path to the folder on Kiwi is a bit clunky but the "copy path" option on Solid Explorer helps with that; or you can do it on PC).

[Cyberavater]

A workaround to avoid the cache deletion issue is packaging the extension folder into a CRX via the Pack Extension option and then installing the resulting CRX (putting the full path to the folder on Kiwi is a bit clunky but the "copy path" option on Solid Explorer helps with that, or you can do it on PC).

Thanks!

[Delphox]

On another note, if you wanna use Universal Bypass on Kiwi I'd actually recommend using the Edge version's CRX, as it has Edge store's update URL on its manifest so it should auto-update unlike the Chromium ZIP release which has no update URL at all. Here's a link to download it through Edge webstore's API.

Kinda wish Kiwi could download Edge addons natively but I assume it's tricky to spoof as I already tested and a simple user-agent spoof isn't enough like it is on Opera's addon store. So it's prolly out of scope.

[Delphox]

(tagging @kiwibrowser to check if he agrees or if I'm missing something and it's actually doable)

[Cyberavater]

Yes, it'd be nice if Kiwi could download Edge add-ons natively. Should I open a new issue regarding that?

[kiwibrowser]

The separate issue is better @Cyberavater
(as a side-note, I'm not familiar at all with how the store for Edge add-ons is working)