Note: If you have a problem that needs troubleshooting, please refer to the relevant section in the documentation.
Currently, Faux Pas cannot inspect code written in Swift. It can, however, inspect other parts of your project as usual (including Objective-C source code.) Adding Swift support is currently being considered and evaluated.
Sure!
Most of the rules do not expect the checked project target to be an app, and the ones that do disable themselves when they notice that the target type is something else.
Faux Pas checks Xcode projects, so workspaces that consist of projects are supported in the sense that each project can be checked separately.
If the projects included in your workspace can be built independently, you don’t need to do anything special to check them. If, however, they cannot be built independently (and must be built as part of the workspace), you need to tell Faux Pas which workspace and scheme to use.
No — avoid getting a false sense of security from the lack of diagnostics.
Like any other static checker, Faux Pas has false negatives: there are some issues it doesn’t even attempt to find, as well as some variants of issues it tries to find, but can’t.
Diagnostics produced by Faux Pas are (hopefully!) useful information — the lack of them is not.
Usually yes — normally the configuration file is project-specific so it should be part of the project’s repository.
Faux Pas can optionally (with the user’s permission) send an anonymous system profile when it checks for updates. Other than that there are no “tracking” features or analytics of any kind.
The following is a comprehensive list of situations where Faux Pas sends network requests to a server:
Licensing terms are specified in the license agreement. This FAQ document attempts to clarify some aspects of the license agreement.
As many as you want.
Yes. Please get in touch: Contact
If the person for whom you have an Organization Seat License leaves your organization (i.e. they are no longer an employee, independent contractor or a temporary worker of your organization), you may transfer the license to another employee.
If the person for whom you have an Organization Seat License is still employed by your organization, you may transfer the license to another employee only with written permission (via Contact).