Able to verify various settings in ipa file

Verifies that the built app was built using the expected build resources. This is relevant for people who build on machines that are used to build apps with different profiles, certificates and/or bundle identifiers to guard against configuration mistakes.

Supported platforms ios
Author @CodeReaper

1 Example

  provisioning_type: "distribution",
  bundle_identifier: "com.example.myapp"


Key Description Default
provisioning_type Required type of provisioning
provisioning_uuid Required UUID of provisioning profile
team_identifier Required team identifier
team_name Required team name
app_name Required app name
bundle_identifier Required bundle identifier
ipa_path Explicitly set the ipa path
build_path Explicitly set the ipa, app or xcarchive path

* = default value is dependent on the user's system


To show the documentation in your terminal, run

fastlane action verify_build


It is recommended to add the above action into your Fastfile, however sometimes you might want to run one-offs. To do so, you can run the following command from your terminal

fastlane run verify_build

To pass parameters, make use of the : symbol, for example

fastlane run verify_build parameter1:"value1" parameter2:"value2"

It's important to note that the CLI supports primitive types like integers, floats, booleans, and strings. Arrays can be passed as a comma delimited string (e.g. param:"1,2,3"). Hashes are not currently supported.

It is recommended to add all fastlane actions you use to your Fastfile.

Source code

This action, just like the rest of fastlane, is fully open source, view the source code on GitHub

Back to actions