You may occasionally get a warning message looking like this:
Correcting bad FingerPhase transition (FingerPhase.Began skipped)
This warning message isn't really something to worry about unless you get it very often. It typically occurs when an finger input phase is missed/skipped between two frames. Instead of going through the expected phase transition sequence A > B > C, the finger/touch went directly from phase A to phase C, skipping phase B in the process. FingerGestures tries to catch these scenarios and fix them as best as possible, but it gives you a warning when it happens.
This happens the most in low-performance contexts such as low FPS or while testing your app via the Unity Remote.