Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

[Bug] iOS DatePicker only displays the last two digits of the year #13918

Closed
brianjtools opened this issue Mar 3, 2021 · 0 comments · Fixed by #14573
Closed

[Bug] iOS DatePicker only displays the last two digits of the year #13918

brianjtools opened this issue Mar 3, 2021 · 0 comments · Fixed by #14573

Comments

@brianjtools
Copy link

Description

Xamarin Forms 5.0.0.2012 on iOS (14.04) only displays the last two digits of the year where previously displayed all four.

Steps to Reproduce

  1. Implement a DatePicker in an iOS Forms app and set range from 1/1/1600 to 12/31/2399.
  2. Run with iOS simulator
  3. Picker will display the date as M/d/yy i.e. 3/2/21
  4. Select another date and the picker still only displays the year as the last two digits.

Expected Behavior

3/1/2021

Actual Behavior

3/1/21

Basic Information

Only occurs with iOS not Android or UWP. When doing date ranges which span centuries user will not know which century is being displayed.

  • Version with issue: 5.0.0.2012
  • Last known good version: 4.3.0.991211
  • Platform Target Frameworks:
    • iOS:
    • 12.04
  • NuGet Packages:
  • Xamarin.Forms
  • Affected Devices:
    iPhone iPad

Environment

Microsoft Visual Studio Community 2019
Version 16.8.5
VisualStudio.16.Release/16.8.5+31005.135
Microsoft .NET Framework
Version 4.8.04084

Screenshots

Simulator Screen Shot - iPhone 12 - 2021-03-01 at 14 02 28

@brianjtools brianjtools added s/unverified New report that has yet to be verified t/bug 🐛 labels Mar 3, 2021
@samhouts samhouts added this to New in Triage Mar 3, 2021
@PureWeen PureWeen added this to To Fix in 5.0.0 SR 4 (Planning) via automation Mar 3, 2021
@PureWeen PureWeen moved this from New to Ready For Work in Triage Mar 3, 2021
@PureWeen PureWeen removed the s/unverified New report that has yet to be verified label Mar 3, 2021
@Redth Redth moved this from Ready For Work to Needs Estimate in Triage Mar 4, 2021
@jsuarezruiz jsuarezruiz moved this from To Fix to Issue In progress in 5.0.0 SR 4 (Planning) Sep 15, 2021
@jfversluis jfversluis removed this from Issue In progress in 5.0.0 SR 4 (Planning) Oct 5, 2021
@jfversluis jfversluis moved this from To Fix to PR Needs Review in 5.0.0 SR6 (Planning) - Target Date Oct. 13th Oct 5, 2021
@jfversluis jfversluis moved this from To Fix to PR Needs Review in 5.0.0 SR7 (Planning) - Target Date Nov. 10th Oct 18, 2021
@jfversluis jfversluis moved this from To Fix to PR Needs Review in 5.0.0 SR8 (Planning) - Target Date Dec. 15th Nov 17, 2021
@jfversluis jfversluis moved this from To Fix to PR Needs Review in 5.0.0 SR9 (Planning) - Target Date Jan. 19th Dec 23, 2021
Triage automation moved this from Needs Estimate to Closed Dec 23, 2021
5.0.0 SR9 (Planning) - Target Date Jan. 19th automation moved this from PR Needs Review to Done Dec 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Triage
  
Closed
Development

Successfully merging a pull request may close this issue.

2 participants