-
Notifications
You must be signed in to change notification settings - Fork 213
Extensions do not work with Orion browser for iOS #887
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.
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
Comments
Same problem. Successfully worked on Chrome/Edge/Android Kiwi/Mac Orion. But for iOS Orion, not. |
Thanks for contributing to CRXJS! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within 7 days. |
Commenting to keep this issue open. This library is still not a valid choice for me because I need my extensions to work on all platforms (desktop/ios/android). Keeping this issue open makes it easier for people to know that this still doesn't work with Orion on iOS, rather than find out later, and makes it easy to discuss possible solutions. |
This is an automated message. Please do not reply to this comment. |
Build tool
Vite
Where do you see the problem?
Describe the bug
When working on my CRXJS project, I noticed that the extension doesn't load on the Orion browser app for iOS. I have created a minimal CRXJS project to replicate the issue, and it seems like any extension created with CRXJS do not work (a non-CRXJS extension made with simple HTML/CSS or with the Plasmo react framework will work). The extension simply adds a div to google.com with a hello message with React. While it works on Orion for macOS, it does not load at all on the iOS application (it will let you install it, but nothing will show up on the page indicating the extension did not work).
Below, I have added a link to the repo which replicates the issue and more details.
Reproduction
https://github.com/kirankunigiri/crxjs-orion-test
Logs
No response
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: