Closed dboyer closed 10 years ago
Definitely related to the mobile apps. I added a new alert at the same tree and it didn't save with any time stamp, much less one with 00:00:00.
Does it happen with iPhone, too? I'd prefer that the API be validating and formatting the data type that the mobile apps are sending as it persists them. @jwalgran?
@mmcfarland Just getting to testing the iPhone app. I'll let you know.
It seems to also be happening on the iPhone app but not every time, which is weird. The attached screenshot is for tree /latreemap/features/435800/ on the release server. I added all four alerts and actions via the release build of the iOS app.
This is related to OpenTreeMap/OTM2#1046. Basically, we're not doing any date formatting on UDF dates on the website when displaying them (They shouldn't be in YYY-MM-DD format, and definitely shouldn't show time, just date).
@maurizi Do you think this is an exclusively server side issue and we should move this over to the OTM2 repo?
@jwalgran Yes I do. It's more noticeable because the mobile apps send up time as well as date information, but the correct fix is proper date formatting anyways, and thats a server issue, not an issue with the mobile apps.
Closing since this will be handled by OpenTreeMap/OTM2#1046. Labeling as "Verified" to get it off of the closed issues to be verified report. Unblocking because we decided to ship a future server-side fix for this.
Testing with Android app release build 153 and comparing to the tree at latreemap/features/435832/ on the release environment.