-
Notifications
You must be signed in to change notification settings - Fork 105
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
Added Safari Extension #4722
base: master
Are you sure you want to change the base?
Added Safari Extension #4722
Conversation
You forgot to do an installation guide bypassing the app store on iOS (IMO the hardest) and the Apple Store on macOS. You can make them in a similar format to the readme.md file. |
Wow, really amazing work and really appreciated. Going to try to install this asap on a VM and see if it is all working. |
I'd be happy testing. I own a 1st gen iPhone SE but don't have reliable access to a Mac. |
I believe this can be linked to https://support.apple.com/en-gb/guide/mac-help/mh40616/mac for macOS and for iOS it might change with iOS 17 - at least in the EU. Practically speaking, iOS sideloading is nothing for the average user at the moment. Developers can be linked to e.g sideloadly. It seems as if the AppStore deployment isn't a blocker anyway. |
@OhMyGuus I have an Apple Developer account and would be happy to get the binary notarized (signed) if that's something you're interested in (if so, feel free to reach me at hello[at]samspencer[dot]art) |
Changes
Notes
The included Safari extension requires Xcode to build, compile, and distribute. Because Safari extensions must be distributed as part of an app bundle, the extension must also be code-signed. On macOS, the extension will need to be notarized in order to install and run without showing warnings to users. @OhMyGuus let me know if you need a hand with any of this.