Amazon Timestamp bug. json changed from string to int

[justinmadison]

Amazon updated this weekend and the timestamp is being sent out as an int instead of an ISO 8601 formatted string (i.e., 2015-05-13T12:34:56Z).

This causes the error "json: cannot unmarshal number into Go struct field EchoReqBody.timestamp of type string"

My guess is this is a bug they will fix so I don't think an update to skill server is required. Thought I would post an issue incase someone using the package is having a problem

[mikeflynn]

Thanks for the heads up!

[davent]

For what it's worth, this does appear to be a bug. It the request originates from the Amazon Developer console testing facility then the timestamp is sent as an integer. However, if the request originates from an Echo device (only tested with an Echo) it is sent as a string.

[mikeflynn]

I've been traveling and unable to check in on this, but is this still and issue with Amazon's servers?