Resolving UNIX Timestamp and Timezone Issues in Zano and Bubble

The State Changers had a productive meeting, where they discussed various topics mainly focused on system timestamps and dealing with time zone differences. They started by working on how to display UNIX timestamps correctly in the Bubble platform. After dedicated troubleshooting, they discovered that timestamps from Zano are returned in milliseconds while Bubble's API backend expects seconds. The solution involved creating a new variable on Zano, dividing the original timestamp by one thousand to convert milliseconds into seconds, and then using that value for Bubble.

Later, the topic shifted towards handling different time zones effectively. The requirement was to return only the records that were within working hours set for a particular location, taking into account their respective time zone differences. The proposed solution was to store the time zone offset for each location and perform mathematical calculations to add this offset to the current GMT time. This way, they could determine local time in each zone. They also discussed considering Daylight Savings changes and the potential need to run the offset occasionally, to keep the offset accurate. Tabled solutions suggest a balance between computational accuracy and performance. Technologies and tools mentioned in the discussion were Bubble, Zano, UNIX timestamps, and dealing with time zones. There was no mention of other keywords like WeWeb, FlutterFlow, Zapier, Make, Integromat, Outseta, Retool, Adalo, AppGyver, AppSheet, Comnoco, Fastgen, Firebase, Google, OAuth, Stripe, Twilio, Airtable, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, State Change, ScriptTag, OpenAI, and AI21.

(Source: Office Hours 9/29 PM )

State Change Members Can View The Video Here

View This Video Now

Join State Change Risk-Free