8000 Using Proxy Service in Safari throws an error if called from an Injected script · Issue #86 · aklinker1/webext-core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

Using Proxy Service in Safari throws an error if called from an Injected script #86

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
thianphat opened this issue Dec 26, 2024 · 5 comments
Closed

Using Proxy Service in Safari throws an error if called from an Injected script #86

thianphat opened this issue Dec 26, 2024 · 5 comments

Comments

@thianphat
Copy link
thianphat commented Dec 26, 2024 •
edited
Loading

First off, thank you so much for this amazing package. I've refactored my codebase to be much more manageable and straightforward.

However, I did notice this one issue where you call a registered Proxy Service from an Injected script's UI (using React, not sure if that matters) and it throws this error. Any idea on what might be causing it? The error does not appear in Safari's console.

This works flawlessly on Chrome.

Thanks!

Screenshot 2024-12-26 at 9 23 52 AM
@aklinker1
Copy link
Owner
aklinker1 commented Dec 26, 2024 •
edited
Loading

This package uses the webextension-polyfill, which has some known issues with Safari and messaging using the promise API. Add this code at the beginning of your background script: mozilla/webextension-polyfill#234 (comment)

@thianphat
Copy link
Author

mozilla/webextension-polyfill#234 (comment)

added this, but it's still encountering the same error

Screenshot 2024-12-26 at 10 00 28 AM

@aklinker1
Copy link
Owner
aklinker1 commented Dec 26, 2024 •
edited
Loading

Hmm, then I'm not sure. The error message isn't providing any useful information, so I don't even know where the problem might be.

I've used this package on Safari before and it works just fine.

@thianphat
Copy link
Author

I think it has to do with Safari service workers being non-responsive: https://developer.apple.com/forums/thread/764594 and not with your package itself.

@aklinker1
Copy link
Owner

OK, then I'm gonna close this issue. If you find out more and it is related to this package, feel free to reopen.

@aklinker1 aklinker1 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aklinker1 @thianphat
0