Build native iOS mobile applications with Bini.js.
Bini.js allows you to build native iOS mobile applications using Tauri v2. Your React app runs inside a WKWebView with full access to native iOS APIs and features.
Real native WKWebView, not a wrapper
Xcode-managed automatic signing
bini-native wires iOS permissions
Building iOS apps requires different tools depending on your operating system. See the section for your OS below.
.app directly from Windows or Linux. Tauri v2 has no supported local cross-compilation path for iOS. The recommended way is GitHub Actions on a macos-latest runner, described in each section below.On macOS you can scaffold, develop, and build the iOS app entirely on your own machine - no CI required.
20.19.0 or higherxcode-select --installsudo gem install cocoapodsCreate a new Bini.js project targeting iOS, install its dependencies, and install its pods:
Or run the interactive prompt and select iOS:
Run ios to launch on the simulator or a connected device, then ios:build to produce the app bundle:
Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:
A native iOS .app cannot be produced on Windows - Tauri relies on Xcode, Apple's signing toolchain, and CocoaPods, none of which run on Windows.
Since the scaffold does not offer iOS as an option on Windows, you should first scaffold an Android project, develop and test your app there, and then let GitHub Actions build the iOS app for you.
npx create-bini-app@latest my-app --platform androidnpm run android.npm run deploy and choose iOS.Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:
macos-latest is the supported path.A native iOS .app cannot be produced on Linux - Tauri relies on Xcode, Apple's signing toolchain, and CocoaPods, none of which run on Linux.
Since the scaffold does not offer iOS as an option on Linux, you should first scaffold an Android project, develop and test your app there, and then let GitHub Actions build the iOS app for you.
npx create-bini-app@latest my-app --platform androidnpm run android.npm run deploy and choose iOS.Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:
macos-latest is the supported path.Running ios opens your app on the iOS Simulator or a connected device. This requires a Mac with Xcode installed (see the macOS section):
This launches your app with:
bini-nativenpm run iosBuild a distributable iOS app. On macOS this runs locally; on Windows and Linux it runs in GitHub Actions (see those sections):
The build outputs land in src-tauri/gen/ios/:
my-app.app - iOS app bundle (for simulator/testing)my-app.ipa - iOS App Store package (for distribution)Bini.js supports Developer ID signing and notarization for macOS binaries. Set it up or redo it at any time with create-bini-app sign. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires an Apple Developer account. If you do not have one, enroll in the Apple Developer Program.
.p12 file (for CI builds)..p12 file..mobileprovision) for CI builds, or use Xcode's automatic signing for local development.For local development, Xcode handles signing automatically. You can either open the project in Xcode or run:
In Xcode, select the project → Signing & Capabilities → choose your Team.
If you want the GitHub Action runner to sign the .ipa automatically, you must provide the certificate and provisioning profile via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:
To sign and notarize the macOS build in GitHub Actions, you must add your credentials as repository secrets. bini-deploy does not upload secrets automatically. You must add them manually:
IOS_CERTIFICATE with the base64-encoded string of your .p12 file.IOS_CERTIFICATE_PASSWORD with the password for your certificate.IOS_MOBILE_PROVISION with the base64-encoded string of your .mobileprovision file.APPLE_DEVELOPMENT_TEAM with your Apple Team ID.APPLE_API_ISSUER, APPLE_API_KEY, and APPLE_API_KEY_P8 (or use APPLE_ID, APPLE_PASSWORD, APPLE_TEAM_ID).You can build the iOS app locally on macOS using npm run ios:build, or let GitHub Actions build it for you by running npm run deploy.
npm run deploy generates .github/workflows/ios.yml and pushes your project to GitHub:
npm run deploy to generate the CI workflow and push to GitHub.Once you have a signed .ipa or .app, you can distribute it. Depending on your goals, you have two options:
.ipa to App Store Connect for beta testing with external users..ipa to the App Store for public release.TestFlight allows you to distribute beta builds to up to 10,000 external testers. Upload the .ipa to App Store Connect (via Xcode, Transporter, or the App Store Connect API), and invite testers via the App Store Connect dashboard. See the TestFlight guide for the specific steps.
To publish on the App Store, you need an Apple Developer Program membership. Upload the .ipa to App Store Connect, fill out the app metadata and screenshots, and submit it for review. See the App Store submission guide for the specific steps.
ios:build. For distribution, you must use App Store Connect.Build a native Android app with keystore signing and Play Store support.
Build a native Windows app with Authenticode signing and NSIS/MSI installers.
Build a native macOS app with Developer ID signing and notarization.
Build a native Linux app with AppImage, .deb, and .rpm bundles.
Build native iOS mobile applications with Bini.js.
Bini.js allows you to build native iOS mobile applications using Tauri v2. Your React app runs inside a WKWebView with full access to native iOS APIs and features.
Real native WKWebView, not a wrapper
Xcode-managed automatic signing
bini-native wires iOS permissions
Building iOS apps requires different tools depending on your operating system. See the section for your OS below.
.app directly from Windows or Linux. Tauri v2 has no supported local cross-compilation path for iOS. The recommended way is GitHub Actions on a macos-latest runner, described in each section below.On macOS you can scaffold, develop, and build the iOS app entirely on your own machine - no CI required.
20.19.0 or higherxcode-select --installsudo gem install cocoapodsCreate a new Bini.js project targeting iOS, install its dependencies, and install its pods:
Or run the interactive prompt and select iOS:
Run ios to launch on the simulator or a connected device, then ios:build to produce the app bundle:
Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:
A native iOS .app cannot be produced on Windows - Tauri relies on Xcode, Apple's signing toolchain, and CocoaPods, none of which run on Windows.
Since the scaffold does not offer iOS as an option on Windows, you should first scaffold an Android project, develop and test your app there, and then let GitHub Actions build the iOS app for you.
npx create-bini-app@latest my-app --platform androidnpm run android.npm run deploy and choose iOS.Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:
macos-latest is the supported path.A native iOS .app cannot be produced on Linux - Tauri relies on Xcode, Apple's signing toolchain, and CocoaPods, none of which run on Linux.
Since the scaffold does not offer iOS as an option on Linux, you should first scaffold an Android project, develop and test your app there, and then let GitHub Actions build the iOS app for you.
npx create-bini-app@latest my-app --platform androidnpm run android.npm run deploy and choose iOS.Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:
macos-latest is the supported path.Running ios opens your app on the iOS Simulator or a connected device. This requires a Mac with Xcode installed (see the macOS section):
This launches your app with:
bini-nativenpm run iosBuild a distributable iOS app. On macOS this runs locally; on Windows and Linux it runs in GitHub Actions (see those sections):
The build outputs land in src-tauri/gen/ios/:
my-app.app - iOS app bundle (for simulator/testing)my-app.ipa - iOS App Store package (for distribution)Bini.js supports Developer ID signing and notarization for macOS binaries. Set it up or redo it at any time with create-bini-app sign. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires an Apple Developer account. If you do not have one, enroll in the Apple Developer Program.
.p12 file (for CI builds)..p12 file..mobileprovision) for CI builds, or use Xcode's automatic signing for local development.For local development, Xcode handles signing automatically. You can either open the project in Xcode or run:
In Xcode, select the project → Signing & Capabilities → choose your Team.
If you want the GitHub Action runner to sign the .ipa automatically, you must provide the certificate and provisioning profile via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:
To sign and notarize the macOS build in GitHub Actions, you must add your credentials as repository secrets. bini-deploy does not upload secrets automatically. You must add them manually:
IOS_CERTIFICATE with the base64-encoded string of your .p12 file.IOS_CERTIFICATE_PASSWORD with the password for your certificate.IOS_MOBILE_PROVISION with the base64-encoded string of your .mobileprovision file.APPLE_DEVELOPMENT_TEAM with your Apple Team ID.APPLE_API_ISSUER, APPLE_API_KEY, and APPLE_API_KEY_P8 (or use APPLE_ID, APPLE_PASSWORD, APPLE_TEAM_ID).You can build the iOS app locally on macOS using npm run ios:build, or let GitHub Actions build it for you by running npm run deploy.
npm run deploy generates .github/workflows/ios.yml and pushes your project to GitHub:
npm run deploy to generate the CI workflow and push to GitHub.Once you have a signed .ipa or .app, you can distribute it. Depending on your goals, you have two options:
.ipa to App Store Connect for beta testing with external users..ipa to the App Store for public release.TestFlight allows you to distribute beta builds to up to 10,000 external testers. Upload the .ipa to App Store Connect (via Xcode, Transporter, or the App Store Connect API), and invite testers via the App Store Connect dashboard. See the TestFlight guide for the specific steps.
To publish on the App Store, you need an Apple Developer Program membership. Upload the .ipa to App Store Connect, fill out the app metadata and screenshots, and submit it for review. See the App Store submission guide for the specific steps.
ios:build. For distribution, you must use App Store Connect.Build a native Android app with keystore signing and Play Store support.
Build a native Windows app with Authenticode signing and NSIS/MSI installers.
Build a native macOS app with Developer ID signing and notarization.
Build a native Linux app with AppImage, .deb, and .rpm bundles.