You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- FlutterFlow version: FlutterFlow v5.4.3 released April 16, 2025
- Platform: Web
- Browser name and version: Edge
- Operating system and version affected: Windows 10
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Hi! I'm sorry you're experiencing this issue. What’s happening is that the jm format is locale-dependent.
In English (en), jm is interpreted as h:mm a (12-hour format with AM/PM).
However, in other languages like Spanish (es), French (fr), etc., the default convention is to use the 24-hour format. So jm returns something like 17:30 without AM/PM.
But no worries! Here’s a simple workaround:
Set the DateTime format to custom and use the following format:
h:mm a
If I understood correctly, this should return the format you're expecting.
Thanks, @Juansarmi. Very thoughtful of you. Just out of curiosity, is it possible to make jm not local-dependent? Cause this doesn't happen using code, so I still see it as an issue.
Hi again! I'm glad to hear that this solved your issue. You can also set the project language to English (or another language where this format is standard), and that should make "jm" display in the desired format.
Can we access your project?
Current Behavior
The current behavior displays 24h format hour and apparently the issue is only on interface settings, but under custom code those formats work well.
Expected Behavior
The format should return 8:00 am.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT88lMmAx89OxcRE7aX6bsEwoCURNjsja7ssltZxYw81F4jyPIYEfPTOVE5AXsDmSlFIPVqcgUUG086LuPKeDe04H02ub4hg+L9XdzzyfDm6V7abCYeNP0EmEp5YCFPF1KeriCUnB/NzWiEf6ju1eufIQhXvGL7MPUQZIPyhKoDJ+WCXLiPjEyYzwREJIGreTI5ODEz25eKMrop5yfj/0w==
Visual documentation
Environment
Additional Information
No response
The text was updated successfully, but these errors were encountered: