[RESOLVED] Safari extension built with plasmo says it’s Chrome -and doesn’t work.

Pasithea0

Not sure where to start. I have an extension that was successfully ported to Safari with plasmo by a contributor.

I can build a binary that installs in Safari, but when I try to add the same binary to Orion it thinks it’s a chrome extension and doesn’t work. I suspect it’s trying to translate the calls, but it shouldn’t because it’s built for Safari.

https://github.com/trinityhades/safari-extension/releases/tag/release

I’ve tried packing it as a .appex using Xcode but it still doesn’t work, probably just due to the structure of the extension.

Any help would be appreciated!

It's meant to connect to https://pstream.mov/onboarding/extension

0.99.136-beta

Tahoe (26)

Pasithea0

And no, the chrome or Firefox build doesn’t work here either. It uses DNR, which I don’t think Orion supports converting to yet, so a safari version was needed

Pasithea0

Ok turns out the issue of it not working is an unrelated plasmo issue. I'll make a new issue.

Now that I've looked closer at this extension, I dont think there is a way to resolve this. Plasmo doesnt see to have a native webkit framework, so this extension manually calls the APIs if it detects it's in a safari extension environment. So resolving this issue would only fix maybe a handful of extensions.

Pasithea0

Wow... So turns out webkit's declarative net request api is "incomplete"??? So my extension wouldn't even work if I got plasmo's messaging to work. I need it to modify request headers, and it just wont work. Sad.

I followed up to this thread because I discovered the runtime messaging was broken but now I guess I'll follow up on the DNR one from a while back.