Error: Failed to generate auth token

[sentry-io]

Sentry Issue: ORIGIN-DAPP-RZ

Error: Failed to generate auth token
  at t.default.loginWithSign (/app.51465dcd.js:120:222780)

[micahalcorn]

This occurs when people try to sign in to the DApp. It has been reported by a handful of people in #bug-reports. 🙁

[shahthepro]

@micahalcorn I checked the logs, it seems like the timestamp (in the signed payload) is at least 10 mins ahead of current time. At present, we have an offset of 5 mins to account for the clock differences among client. i.e. The sign will be considered valid even if it is 5 mins in future. I can increase this to something like 15 mins

[micahalcorn]

@shahthepro thanks, any consequence to doing that? 🤔

[shahthepro]

@micahalcorn Shouldn't be, since 15 minutes isn't that long in the future. I just opened a PR for that

[micahalcorn]

Considering this done 🤞

[micahalcorn]

@shahthepro @tomlinton I haven't reproduced this issue, but I just noticed that, in our app, my clock in my status bar in Origin Marketplace is completely wrong. It never seems to change from 1:41 and my time is currently 16:57. That probably has nothing to do with this issue since the reports are coming from non-Origin environments. And for what it's worth, users are reporting that their clocks are accurate. 🤷‍♂

[tomlinton]

Screenshot? I don't see a clock in the status bar at all, are you looking at Android?

[micahalcorn]

@tomlinton bizarre 😳 I don't see one now either. It must have been a glitch on my phone.

[shahthepro]

@micahalcorn @tomlinton After #4237, I see this less frequent on the logs. But the ones that still do happen have timestamp that exactly an hour behind. Not sure if DST has anything to do with this.