If you're seeing this it's my guess that the GDS implemented a new seat map API that was slightly different from the old one which they shut off, something that has happened several times in the past, but the parsing of the new API vs the old API wasn't double checked. To help them, email support with a specific, reproducible example of a flight more than a few days in the future, with a screen shot of the seat map from AA.com for comparison, pointing out the specific differences of seat type. Hopefully they'll figure it out (this is the kind of stuff I used to do).