Hey Kevin,
Thanks for the clarification. I do agree that the signature should have all the params, and that this was a good fix. We just didn't expect the changes to happen over the weekend, as we've been building our app around the previously 'bugged' signature calculations.
I do want to suggest something going forward though: Changelogs for EASDK changes before or when they get rolled out. Right now there doesn't seem to be a way to track bugs in the EASDK as well as what's change or what's been fixed.
As for #1, do keep us updated as to when the fix is made. Thanks again for all the help.
Celso: I wasn't talking about the App Preferences link specifically, but that before the weekend, the signature calculations did not involve non-shopify parameters, meaning "http://www.example.com?foo=bar×tamp=1&shop=test" would have the same signature as http://www.example.com?timestamp=1&shop=test"
Thanks.
-Mathias