lime peak
@cold junco (Android) and me (web) see the following error appearing for some users InvalidSignatureException errors:
{"Message":"Signature expired: 20231012T132654Z is now earlier than 20231012T132705Z (20231012T133205Z - 5 min.)"}
Likely it's their the clock of the users device being out of sync.
@lethal rivet is this a know issue that you know of?
lethal rivet
Correct. This appears to be a users clock out of sync.
lime peak
Thanks for confirming @lethal rivet ! For your information: out of all Liveness errors on Sentry for our user base, this consists of 50% of all errors.
lethal rivet
Depending on your customer user base location, we have observed that some regions have implemented DST (however, Android manufacturers have not updated the devices to properly reflect these changes). This has resulted in the customer manually changing times and being off 1+ hrs
lethal rivet
@lime peak Liveness 1.1.5+ has a build in correction to handle this error with no changes on your part required.