My App
Frameworks

iOS (Native)

Setup guide for distributing native Swift and Objective-C iOS applications using Xcode and Fastlane.

🍎 Native iOS (Xcode)

Distributing iOS builds requires archiving the application target and exporting it as a signed IPA (iPhone Application Archive) file using appropriate Ad-Hoc or Enterprise provisioning profiles.


📁 Typical Build Paths

iOS builds are compiled into a custom DerivedData folder by default. We recommend configuring a specific local export target path for your compiled .ipa file:

  • iOS IPA: ./build/MyApp.ipa (or exported Xcode folder path)

Initialize the build path configuration in your iOS workspace folder:

buildshare init \
  --project-name "Native iOS App" \
  --package-name "com.example.nativeios" \
  --ios-path "./build/MyApp.ipa"

Fastlane is the industry standard for automating iOS compilation and signing. You can easily integrate BuildShare CLI as a shell action inside your pipeline.

Add the following lane configuration to your fastlane/Fastfile:

desc "Build and upload release to BuildShare"
lane :distribute do
  # 1. Archive and package your iOS app into an IPA
  gym(
    scheme: "MyApp",
    output_directory: "./build",
    output_name: "MyApp.ipa",
    export_method: "ad-hoc"
  )

  # 2. Upload to BuildShare CLI with custom changelog metadata
  sh("npx buildshare upload ios --file ./build/MyApp.ipa --no-confirm --changelog 'Fastlane automated release'")
end

Now, triggering a release is as simple as:

fastlane distribute

On this page