-
Notifications
You must be signed in to change notification settings - Fork 4.4k
🐛 Bug Report: expire
is not formatted the same as other datetimes
#4982
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
Comments
expire
is not formatted the same as other datetimes
Related issue: #4846 |
To ensure the correct formatting, we should be using appwrite/app/controllers/general.php Line 320 in 514b42b
|
Can I work on this? |
I would like to work on this issue! |
@wharl thanks for your interest, but I've assigned it to @munyoudoum since they asked first. |
I would like to work on this issue, I am familiar with this type of issue |
Other affected APIs:
|
I would like to work on this issue, |
@stnguyen90 |
closes: appwrite#4982 Signed-off-by: Julian Strobl <jmastr@mailbox.org>
Uh oh!
There was an error while loading. Please reload this page.
👟 Reproduction steps
Today I upgraded AppWrite to 1.2.0. The migration went fine. But my client could no longer log in. I traced the problem back to a changed 'expire' format. The screenshots show the result of /v1/account/sessions/email/
The first screenshot shows the result of Version 1.2.0: "expire": "2024-01-09 21:32:12.004"
The second screenshot shows the result of Version 1.0.1: "expire": "2024-01-09T21:22:23.290+00:00"
Notice the missing 'T' and missing trailing '+00:00' which cause my parser to fail. I did not find anything in the release notes.
'$createdAt' has the correct format

👍 Expected behavior
expire should have standard format.
👎 Actual Behavior
expire does not have the standard format, breaking the parser
Other affected APIs:
expire
Format is Wrong in Create Magic URL session (confirmation) #5428expire
Format is Wrong in Get Session #5429🎲 Appwrite version
Version 1.2.x
💻 Operating system
Linux
🧱 Your Environment
Backend to my app
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: