Posting purely because I’m wondering if anybody else has started seeing this psuedo-millennium bug.
I’m sending dates in a very basic capacity to bubble’s API, formatted as yyyy-mm-dd, which has worked fine for 2 years up until now (and in theory should be valid quite generally).
What has started occurring in the last week or so is that dates like “2024-07-12” have been resolving to “Jan 1st, 1970”. The only tangible change I’ve made was using bubble’s cleanup tool for the first time, having previously been too scared of the platform’s instability to use what felt a bit like a shotgun blast to the db.
Will submit a bug report shortly, but am curious to see if anybody else has experienced this behaviour before.
Off the top of my head, I do know that Bubble has made changes to timezone handling within the past couple years, but those changes were in a versioned release of the platform.
Have you by chance recently updated your app to the latest version of the Bubble platform? If so, perhaps it’s related. If not, additional context and detail (and maybe screenshots) might enable others to better assist.
Thanks for getting back, turns out one of my employees unknowingly added spaces to a csv column header. Feeling quite silly about this post now, as I was seeing the blocks returned by the file uploader and thinking my regex was successfully extracting the date value, when in fact it was receiving null.
Interesting that it didn’t error however, which is what I’d expect from bubble, instead defaulting to Epoch which I haven’t actually seen before.
Haha yep, was not altogether too impressed, but sorted in the end.
It makes sense for sure, more mean that I’ve sent blank dates to bubble in the past and received an error code to the tune of “expected date but received string” or similar. Maybe some weird edge case change that I’ve run into, who knows!
Anyway thanks for trying to help at least, much appreciated
