Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Android][Inconsistency with desktop] [Date input component does not honour the default value] #3671

Closed
shbhadra opened this issue Dec 10, 2019 · 5 comments
Labels
Area-Inconsistency Bugs around renderer inconsistencies across different platforms Bug Partner-MsftTeamsMobile Bugs related specifically to Teams Mobile integration (iOS/Android) Platform-Android

Comments

@shbhadra
Copy link

shbhadra commented Dec 10, 2019

Platform

  • Android

Author or host

Host

Version of SDK

1.2.5

Details

The date input component does not honour the default value and always shows the current date by default. For the card as in the attached json, following are the views on desktop and android.
(https://github.com/microsoft/AdaptiveCards/files/3944744/default_date.json.zip)

View on desktop
image
View on android
Screenshot 2019-12-10 at 5 33 21 PM
default_date.json.zip

{
   "type":"AdaptiveCard",
   "body":[
      {
         "type":"TextBlock",
         "size":"medium",
         "weight":"bolder",
         "text":"Test title"
      },
      {
         "type":"TextBlock",
         "text":"Testing Date input.",
         "wrap":true
      },
      {
         "type":"Input.Date",
         "value":"03/12/2019",
         "id":"date"
      }
   ],
   "$schema":"http://adaptivecards.io/schemas/adaptive-card.json",
   "version":"1.0"
}
@shbhadra shbhadra added the Bug label Dec 10, 2019
@ghost ghost added the Triage-Needed label Dec 10, 2019
@VikrantSingh01 VikrantSingh01 added the Partner-MsftTeamsMobile Bugs related specifically to Teams Mobile integration (iOS/Android) label Dec 13, 2019
@paulcam206 paulcam206 added the Area-Inconsistency Bugs around renderer inconsistencies across different platforms label Jan 7, 2020
@jwoo-msft
Copy link
Member

jwoo-msft commented Jan 7, 2020

Time and Date values have to be expressed in specific format.
Date: YYYY-MM-DD
Time:HH:MM
Resolution: Created PR for updated doc

@shalinijoshi19
Copy link
Member

@nesalang, thanks! Are we now consistent across all renderers/platforms wrt time and date expressions?

@ghost
Copy link

ghost commented Feb 1, 2020

🎉[email protected] has been released which fixes this issue.:tada:

Handy links:

@shbhadra
Copy link
Author

@nesalang @shalinijoshi19 I believe this has been erroneously closed, the issue still persists in the 1.2.6 drop. Note that the bug is not regarding the format of the date, but that the date input element picks up todays date by default, instead of the specified date value.

@jwoo-msft
Copy link
Member

jwoo-msft commented Feb 11, 2020

@shbhadra ,

Thanks for reaching out to us.

{
         "type":"Input.Date",
         "value":"03/12/2019",
         "id":"date"
}

The date string, "03/12/2019", is in wrong format.
The correct format is 2019-03-12 . i.e YYYY-MM-DD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Inconsistency Bugs around renderer inconsistencies across different platforms Bug Partner-MsftTeamsMobile Bugs related specifically to Teams Mobile integration (iOS/Android) Platform-Android
Projects
None yet
Development

No branches or pull requests

5 participants