Thank you for reporting the issue. Our team is looking into this and we will get back to you.
Thank you for your patience,
I checked it in FB4.5 simulator for Android HTC Desire HD (Windows) and on mac FB4.5 simulator (HTC Incredible). For frmtdateOnly, I do see the correct patterm of dd/MM/yyyy (windows simulator, HTC Desire HD), Mac (HTC Incredible) on both. The actualLocaleID is correct;y shown as en-GB.
I did set the locale as en-GB in control panel regional language settings (win) and mac system language settings.
I need to check it on the actual device and see the problem. I will get back to you on this.
This is a device issue not a simulator one. Thanks for looking into it.
When assigning a desired date time pattern to DateTimeFormatter.dateTimePattern property, the property itself is not modified, but the dateTimePatternOverride property is set accordingly. HOWEVER, the latter has no effect whatsoever.
I solved my problem by using the mx formatters, but that is obviously not the desired solution.
1 person found this helpful
I verified it on Google Nexus. Handling i-default does have a bug on android devices.Possible work around is if you can use the locale explicitly en-GB then the bug won't surface. We filed a bug against it for near future fix.
Thanks. The problem with the proposed work around is that you require a setup document for apps that have an international user base.
harish@adobe - has this been fixed? What was the bug #?
I'm still encountering this using Flex 4.6 and Air 3.2.