-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
BadRequestError createdAt must be an valid atproto datetime (both RFC-3339 and ISO-8601) #192
Comments
Noticed that this might be something I did wrong as I had used datetime.datetime.now().isoformat() instead of datetime.datetime.utcnow().strftime("%Y-%m-%dT%H:%I:%SZ") |
By the way, here's how I generate my timestamps, which perfectly matches the output of JS's import datetime
datetime.datetime.now(tz=datetime.timezone.utc).replace(tzinfo=None).isoformat(timespec="milliseconds") + "Z" Also by the way, |
That is really useful to know thanks |
@EllieTheYeen The AT Protocol SDK provides and uses this method internally. Doesn't it feet your needs? from atproto import Client
client = Client()
print(client.get_current_time_iso()) |
Good to know. I had done some wrong thing internally in my code that generated the date so that is what caused the issue and not the code here |
I have started to get the following error whenever I try to post anything at all. I have not made any change in the code but both reposts and normal posts will throw the following error:
I think Bsky has changed something that causes this issue
The text was updated successfully, but these errors were encountered: