Xcode Analyze
Find flaws and potential bugs in the source code of an app with the static analyzer built into Xcode.
Find flaws and potential bugs in the source code of an app with the static analyzer built into Xcode.
The Step uses the static analyzer built directly into Xcode to analyze your app's source code: the static analyzer tries out thousands of possible code paths in a few seconds, reporting potential bugs that might have remained hidden or bugs that might be nearly impossible to replicate.
This process also identifies areas in your code that don't follow recommended API usage, such as Foundation, UIKit, and AppKit idioms.
In most cases, you don't need to change the Step's configuration. The default input values work well if you added your iOS app on the website, using automatic configuration.
To make sure the Step works well for you:
Make sure the Project (or Workspace) path points to the path of the .xcodeproj or .xcworkspace file of your app, relative to the app's root directory.
Make sure the Scheme name input points to a valid shared Xcode scheme. Note that it must be a shared scheme!
Optionally, you can force the Step to use specific code signing identities. To do so, use the Force code signing with Identity and Force code signing with Provisioning Profile inputs.
For detailed instructions on their use, see the inputs themselves.
