I’m having the same issue as described here. I am using a ruby implementation of the signature generation, the relevant code is here:
Note that this signature generation worked as recently as version 1.7.5, a week or so after its release. But somewhere between then and now, this broke.
Today I added the - 30000
to the timestamp and upgraded the plugin to SDK v 1.7.7, but I still suspect that something isn’t right with the time now. So, can we have some clear instructions on whether the timestamp needs to be a specific timezone?
To clarify, using the sample web app, I can join the event, but using the Ruby implementation I can’t.
Update: @deepak2’s code in Invalid Signature with Sample Web App solved my Ruby issue. Thanks Deepak!