This is simply because they're taking an integer from their database as an auto incrementing ID and converting it directly into a native integer on the iOS device thus breaking it. They could work around this any number of ways.

It's a pretty lame bug, to be honest and certainly something easily foreseeable as this wasn't an overnight occurrence.