moonlight-ios/README.md
Kiko 113e352789
Some checks failed
CI / Build (iOS) (push) Has been cancelled
CI / Build (tvOS) (push) Has been cancelled
CI / Build (iOS) (pull_request) Has been cancelled
CI / Build (tvOS) (pull_request) Has been cancelled
README: say the OBS bridge role is planned, not present
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-05 10:50:52 +00:00

2.4 KiB

Moonlight iOS/tvOS

CI

Moonlight for iOS/tvOS is an open source client for Sunshine and NVIDIA GameStream. Moonlight for iOS/tvOS allows you to stream your full collection of games and apps from your powerful desktop computer to your iOS device or Apple TV.

Moonlight also has a PC client and Android client.

Check out the Moonlight wiki for more detailed project information, setup guide, or troubleshooting steps.

Moonlight for iOS and tvOS

Building

  • Install Xcode from the App Store page
  • Run git clone --recursive https://github.com/moonlight-stream/moonlight-ios.git
    • If you've already clone the repo without --recursive, run git submodule update --init --recursive
  • Open Moonlight.xcodeproj in Xcode
  • To run on a real device, you will need to locally modify the signing options:
    • Click on "Moonlight" at the top of the left sidebar
    • Click on the "Signing & Capabilities" tab
    • Under "Targets", select "Moonlight" (for iOS/iPadOS) or "Moonlight TV" (for tvOS)
    • In the "Team" dropdown, select your name. If your name doesn't appear, you may need to sign into Xcode with your Apple account.
    • Change the "Bundle Identifier" to something different. You can add your name or some random letters to make it unique.
    • Now you can select your Apple device in the top bar as a target and click the Play button to run.

GameCult fork: publish health is independent

This fork is meant to take on the OBS bridge role that Ratatoskr used to hold; none of that code exists on this branch yet, so this is a rule for code to come. Whatever Moonlight publishes toward OBS, publish state is its own path, and no other feature may touch it. Sound, and any feature added after it, must never block, delay, or report on the publish path. A silent publish must never read as healthy: no output reads as unknown or failed, never as fine.