starred/YouTube-No-Translation

Fork 0

mirror of https://github.com/YouG-o/YouTube-No-Translation.git synced 2026-04-25 18:16:00 +03:00

[GH-ISSUE #32] Feature Request: Automated Safari .app build in GitHub Actions workflow #29

New issue

Closed

opened 2026-03-04 00:03:11 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 00:03:11 +03:00

Owner

Originally created by @YouG-o on GitHub (Jun 4, 2025).
Original GitHub issue: https://github.com/YouG-o/YouTube-No-Translation/issues/32

Originally assigned to: @YouG-o on GitHub.

Problem

Currently, Safari users cannot easily install the extension because there's no pre-built .app file available in releases. This creates several issues:

End users can't install easily: Regular users who don't know how to build from source cannot use the Safari extension
Manual build requirement: Users must have macOS, Xcode, and technical knowledge to build the .app themselves
Inconsistent release assets: Chrome and Firefox get automatic builds uploaded to releases, but Safari doesn't
Maintainer limitation: The main maintainer cannot build or test Safari releases without macOS access

This means Safari users are effectively excluded from using the extension unless they're developers.

Proposed Solution

Add automated Safari .app build generation to the GitHub Actions workflow (.github/workflows/release.yml) to upload pre-built Safari extensions alongside Chrome and Firefox builds. This would involve:

Adding a macOS job with runs-on: macos-latest
Setting up Xcode Command Line Tools automatically
Running the Safari build process (npm run prepare:safari)
Building the Xcode project programmatically to generate the .app
Uploading the .app file as a release asset (similar to current Chrome/Firefox zips)

This would provide ready-to-install Safari extensions for end users, just like we currently do for other browsers.

Additional Context

Current workflow only builds Chrome and Firefox automatically (see .github/workflows/release.yml)
Safari extension files are in safari-extension/YouTube No Translation/
Manual process requires opening .xcodeproj and building from Xcode
Target users: Regular macOS users who want to install the extension without building from source
This would complete the user experience by making all three platforms equally accessible to non-technical users

Originally created by @YouG-o on GitHub (Jun 4, 2025). Original GitHub issue: https://github.com/YouG-o/YouTube-No-Translation/issues/32 Originally assigned to: @YouG-o on GitHub. ## Problem Currently, Safari users cannot easily install the extension because there's no pre-built .app file available in releases. This creates several issues: 1. **End users can't install easily**: Regular users who don't know how to build from source cannot use the Safari extension 2. **Manual build requirement**: Users must have macOS, Xcode, and technical knowledge to build the .app themselves 3. **Inconsistent release assets**: Chrome and Firefox get automatic builds uploaded to releases, but Safari doesn't 4. **Maintainer limitation**: The main maintainer cannot build or test Safari releases without macOS access This means Safari users are effectively excluded from using the extension unless they're developers. ## Proposed Solution Add automated Safari .app build generation to the GitHub Actions workflow (`.github/workflows/release.yml`) to upload pre-built Safari extensions alongside Chrome and Firefox builds. This would involve: 1. Adding a macOS job with `runs-on: macos-latest` 2. Setting up Xcode Command Line Tools automatically 3. Running the Safari build process (`npm run prepare:safari`) 4. Building the Xcode project programmatically to generate the .app 5. Uploading the .app file as a release asset (similar to current Chrome/Firefox zips) This would provide **ready-to-install Safari extensions** for end users, just like we currently do for other browsers. ## Additional Context - Current workflow only builds Chrome and Firefox automatically (see `.github/workflows/release.yml`) - Safari extension files are in `safari-extension/YouTube No Translation/` - Manual process requires opening `.xcodeproj` and building from Xcode - **Target users**: Regular macOS users who want to install the extension without building from source - This would complete the user experience by making all three platforms equally accessible to non-technical users

kerem

2026-03-04 00:03:11 +03:00

closed this issue
added the
enhancement

help wanted
labels

kerem commented

2026-03-04 00:03:12 +03:00

Author

Owner

@TheBreznsoiza commented on GitHub (Jul 1, 2025):

What about releasing the Safari Extension/App to AltStore? (Classic and/or PAL)?

@TheBreznsoiza commented on GitHub (Jul 1, 2025): What about releasing the Safari Extension/App to AltStore? (Classic and/or PAL)?

kerem commented

2026-03-04 00:03:12 +03:00

Author

Owner

@YouG-o commented on GitHub (Jul 1, 2025):

I don’t know it very well, but I think it’s designed for .ipa apps — not sure it’s appropriate for Safari add-ons (.app). I’d love to try, but there’s still the same problem: I don’t have a Mac.
So for now, the only solution for Safari users is to compile the add-on themselves. Sorry about that!

@YouG-o commented on GitHub (Jul 1, 2025): I don’t know it very well, but I think it’s designed for .ipa apps — not sure it’s appropriate for Safari add-ons (.app). I’d love to try, but there’s still the same problem: I don’t have a Mac. So for now, the only solution for Safari users is to compile the add-on themselves. Sorry about that!

kerem commented

2026-03-04 00:03:12 +03:00

Author

Owner

@matthieuHenocque commented on GitHub (Jul 2, 2025):

May I suggest you to make your app available with Homebrew?

Additionally, I really think this app would be a must have on iOS, as you often can't even access the toggle. I cancelled multiple RSS subscriptions because of this.

Thank you very much, and have a nice day!

@matthieuHenocque commented on GitHub (Jul 2, 2025): May I suggest you to make your app available with Homebrew? Additionally, I really think this app would be a must have on iOS, as you often can't even access the toggle. I cancelled multiple RSS subscriptions because of this. Thank you very much, and have a nice day!

kerem commented

2026-03-04 00:03:12 +03:00

Author

Owner

@Seva41 commented on GitHub (Jul 7, 2025):

I've been doing some research on this, and it looks like while it's possible to automate the build using GitHub Actions and xcodebuild, the resulting app will lack the signing identities tied to each individual user and/or Apple Developer account, which makes it impossible to run the app attached to Safari on someone else's machine.

Unless the app is officially published on the macOS AppStore, there doesn’t seem to be a way to distribute a pre-built version using GitHub alone.

AltStore is designed for .ipa files (iOS/iPadOS), not .app bundles (macOS).
Homebrew Cask might be technically feasible, as there are already some examples of Safari extensions being distributed that way.

@Seva41 commented on GitHub (Jul 7, 2025): I've been doing some research on this, and it looks like while it's possible to automate the build using **GitHub Actions** and `xcodebuild`, the resulting app will lack the signing identities tied to each individual user and/or Apple Developer account, which makes it impossible to run the app attached to Safari on someone else's machine. Unless the app is officially published on the **macOS AppStore**, there doesn’t seem to be a way to distribute a pre-built version using GitHub alone. **AltStore** is designed for `.ipa` files (iOS/iPadOS), not `.app` bundles (macOS). **Homebrew Cask** might be technically feasible, as there are already some [examples](https://www.reddit.com/r/MacOS/comments/y5911u/vimari_now_installable_via_homebrew/) of Safari extensions being distributed that way.

kerem commented

2026-03-04 00:03:12 +03:00

Author

Owner

@YouG-o commented on GitHub (Jul 7, 2025):

I've been doing some research on this, and it looks like while it's possible to automate the build using GitHub Actions and xcodebuild, the resulting app will lack the signing identities tied to each individual user and/or Apple Developer account, which makes it impossible to run the app attached to Safari on someone else's machine.

Unless the app is officially published on the macOS AppStore, there doesn’t seem to be a way to distribute a pre-built version using GitHub alone.

AltStore is designed for .ipa files (iOS/iPadOS), not .app bundles (macOS). Homebrew Cask might be technically feasible, as there are already some examples of Safari extensions being distributed that way.

Good to know thanks. Closing the issue then.
We'll keep manual build only for now then.

@YouG-o commented on GitHub (Jul 7, 2025): > I've been doing some research on this, and it looks like while it's possible to automate the build using **GitHub Actions** and `xcodebuild`, the resulting app will lack the signing identities tied to each individual user and/or Apple Developer account, which makes it impossible to run the app attached to Safari on someone else's machine. > > Unless the app is officially published on the **macOS AppStore**, there doesn’t seem to be a way to distribute a pre-built version using GitHub alone. > > **AltStore** is designed for `.ipa` files (iOS/iPadOS), not `.app` bundles (macOS). **Homebrew Cask** might be technically feasible, as there are already some [examples](https://www.reddit.com/r/MacOS/comments/y5911u/vimari_now_installable_via_homebrew/) of Safari extensions being distributed that way. Good to know thanks. Closing the issue then. We'll keep manual build only for now then.

kerem referenced this issue

2026-03-04 00:03:58 +03:00

[PR #29] [MERGED] Safari compatibility (again!) #120