A logic error in JsonReader causes it to not properly verify the expected field names for extended JSON documents which have unexpected field names. For example, the following JSON document should be rejected:

{ "$timestamp" : { "i" : 1, "t" : 1234 } }

because the extended JSON spec requires that the 't' field precedes the 'i' field. But due to this bug the 'i' field will be treated as the 't' field, and vice versa.

Expected result: JsonReader should throw a JsonParseException