iOS (Native)

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 PathsCopy Anchor Link

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 your exported Xcode archive folder path)

Uploading Your BuildCopy Anchor Link

Once your signed IPA file is exported, upload it using the BuildShare CLI:

buildshare upload ./build/MyApp.ipa --notes "iOS Ad-Hoc build"

Automation with Fastlane (Highly Recommended)Copy Anchor Link

Fastlane is the industry standard for automating iOS compilation and signing. You can easily integrate BuildShare CLI as a shell action inside your Fastlane 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 release notes
  sh("buildshare upload ./build/MyApp.ipa --ci --notes 'Fastlane automated release'")
end

Now, triggering a release is as simple as:

fastlane distribute