-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Cannot read properties of undefined (reading 'match')" in API Gateway request when clock is in future #11677
Comments
@hisham I believe we're having this issue too, with unauthenticated users trying to make a public GraphQL call. It only happens to a small portion of users. How did you figure out the timestamp was in the future? I'm not seeing any sort of timestamp logged in Sentry. |
Sentry at the top of the issue has a red box saying they had a problem processing the error, and if you click on it, it will say something like timestamp is in the future. I ran into issues similar to this (but in different parts of the amplify-js lib) related to people's computer clocks being incorrect. (e.g. #9281). |
@hisham, can you confirm if you started to see this error after upgrading to Amplify v5.2.5? And is the error only happening on browser (i.e. nothing on iOS or Android)? |
Related to #11675 |
yeah seems resolved, thanks! :) |
Before opening, please confirm:
JavaScript Framework
Angular
Amplify APIs
REST API
Amplify Categories
api
Environment information
Describe the bug
If user's clock is in future, user is unable to login and we get a Sentry error reported from aws-amplify lib "Cannot read properties of undefined (reading 'match')" in the DateUtils.getDateFromHeaderString function
Expected behavior
User should be able to login or amplify lib fails gracefully.
Reproduction steps
Code Snippet
// Put your code below this line.
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
See attached Sentry error.
The text was updated successfully, but these errors were encountered: