If you create a feature set XML file where one of the features has the attributes type="0" id="0", then the AAM function LoadFeatureFile will silently ignore this feature and append an extra feature with garbage values. This causes subsequent AAM tasks to fail with a numeric exception. I can't see any reason for such a limitation but I would settle for a note in the documentation and an assertion in the code to complain if such a malformed file is encountered.
Logged In: NO
I am the issue submitter; I can be reached for questions at quark at cs dot utexas dot edu.