buildshare.in
Frameworks

iOS (Native)

Setup guide for distributing native iOS Swift or Objective-C IPA builds via BuildShare CLI.

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

We recommend configuring your export target path for your compiled .ipa file:

  • iOS IPA: ./ios/builds/MyApp.ipa (or ./build/MyApp.ipa)

Uploading Your Build

Once you have initialized your project with buildshare init (setting iosPath to your builds directory), upload automatically:

# Upload via platform auto-discovery
buildshare upload ios --notes "iOS Ad-Hoc build"

You can also upload a specific .ipa file directly by providing your project ID:

buildshare upload ./ios/builds/MyApp.ipa --app <projectId> --notes "iOS Ad-Hoc build"

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

On this page