Deploymate is a static analyzer and as such it is not able to detect runtime, dynamic context of your code. For this reason, Deploymate will sometimes warn you about a specific API usage in a code pattern where you possibly might have a runtime conditional (e.g. [instance respondsToSelector:]). Deploymate cannot detect such cases easily thus it's better to warn you with a false positive than stay silent. Deploymate is constantly being improved to deal with these annoyances and progress is already being made since v1.1.
Update: Deploymate will be dealing with false-positives using #pragma directives. Read more here.
Deploymate is a static analyzer based on Clang/LLVM compiler. Clang is being actively developed and improved every day but sometimes it's not able to detect the availability of a certain API. In such cases Deploymate is not aware of the usage and availability and may not complain about an obvious problem. For this reason, you should not rely 100% on Deploymate analysis and it is highly recommended to also do manual testing.
Deploymate supports XIB and storyboards starting version 1.2. Previous versions do not support IB analysis.
We're currently working on figuring out the best way to achieve this. The problem is that when you've fixed a specific problem you want to mark resolved, you've probably changed your source code quite a bit making it difficult for Deploymate to detect again. In order to be more accurate and not misinterpret your code (and miss an obvious problem), this feature is not yet included in the app until it's working properly.
However, since version v1.2, Deploymate has a #pragma preprocessor directive to help you skip analyzing parts of your code. This can help you target out some of the false positives in a recommended way. See the #pragma article in the knowledgebase section.
YES. As of v1.2 Deploymate has a working command line interface suitable for continuous integration. See CLI article in the knowledgebase section.
Yes, it's true. If you define your deployment OS and/or version in .xcconfig or you do any other weird configuration stuff in one or more of configuration files, Deploymate might not be able to find and interpret those. As it turns out, developers do unexpected, unpredictable, crazy stuff in their configuration files. Go figure.
Update: starting v1.2 support for .xcconfig files has been much improved.
Fastspring expires license download URLs after a few days for security. It's best to keep your license files somewhere safe in case you need it. If you lost it, contact us.
If you have a valid .dmlic file, all you need to do is double click it. Please note that some users are reporting problems with this method on 10.9 Mavericks. If you can't double click the file, you can always just open it via Deploymate Open File dialog (CMD+O).
No. Xcode version 7 and above correctly reports unavailable API usage so implementing Swift support in Deploymate would be redundant. For the time being, Deploymate is an Objective-C tool.