Trying to sort this one out.
I have a Date type to receive via the Bubble API.
I have a Date object created inside of Dropsource.
When I send the Date object it doesn’t work and crashes the mobile app created on Dropsource.
Is there a specific format for a date String (as text) that I can send to Bubble and have it convert it into a Date Date? If there is, how do I set up bubble’s api to receive the date as text string, and then convert it into a Date/Date for use in Bubble’s back end?
Justin you don’t have to do any conversion I’ve said several times.
If you look at thr bubble API spec (swagger), bubble accepts dates as strings formatted as dates.
And there are several formats it will accept.
One of them is Unix timestamp.
Dropsource converts dates to Unix timestamps.
So all you have to do is create the date object in dropsource and bind it to the api and that’s it.
At bubble’s end you don’t need to do conversion.
Bubble understands it.
I keep telling you if your app is crashing its something else and not the date.
Even if the app crashes only when you add the date it may be due to some other actions that run afterwards but not the date transmission.
Turn on the network tab in thr dropsource simulator and check to see if the api call to bubble isn’t been successful.
Hi Sean,
I try and bind:
Dropsource “Date” (collected in parts to variables, then created into a date object) to Bubble “Date” and the result is it crashes.
Dropsource String (formatted as a date Bubble will accept) but I CANNOT bind it to the ‘Date’ element in Bubble.
Is there something I’m not doing properly still?
I guess so. Without seeing what you did it’s hard to tell why its crashing.
It should work.
Try displaying the timestamp of the date variable you want to send to bubble in a text view and see what value you get.
This topic was automatically closed after 70 days. New replies are no longer allowed.
