Date issue with Commcare 1.3

Hi all,

I have had three users using a version of Commcare 1.3
reporting that when they reach a date select question, the phone
responds with a constraint message saying that the question needs to
be answered , despite the question being actually answered. my
colleague Peter also noted the same thing for another version of
Commcare 1.2 . has anyone encountered this? what is the workaround
for this?

Thanks

Joachim

Hi Joachim,

I haven’t encountered that problem myself - but if you send a bug report to
Dimagi with the application files attached (see
https://wiki.commcarehq.org/display/commcarepublic/Bug+Report+Template),
we’ll definitely look into it and let you know when we’ve resolved the
issue.

Thanks,
Amelia

··· On Mon, Jan 16, 2012 at 2:33 PM, joachim mangilima wrote:

Hi all,

I have had three users using a version of Commcare 1.3
reporting that when they reach a date select question, the phone
responds with a constraint message saying that the question needs to
be answered , despite the question being actually answered. my
colleague Peter also noted the same thing for another version of
Commcare 1.2 . has anyone encountered this? what is the workaround
for this?

Thanks

Joachim

Joachim,

Can you send along the domain that you’ve been testing this with so I can
replicate it?

-Clayton

··· On Mon, Jan 23, 2012 at 5:58 AM, Amelia Sagoff wrote:

Hi Joachim,

I haven’t encountered that problem myself - but if you send a bug report
to Dimagi with the application files attached (see
https://wiki.commcarehq.org/display/commcarepublic/Bug+Report+Template),
we’ll definitely look into it and let you know when we’ve resolved the
issue.

Thanks,
Amelia

On Mon, Jan 16, 2012 at 2:33 PM, joachim mangilima joachimm3@gmail.comwrote:

Hi all,

I have had three users using a version of Commcare 1.3
reporting that when they reach a date select question, the phone
responds with a constraint message saying that the question needs to
be answered , despite the question being actually answered. my
colleague Peter also noted the same thing for another version of
Commcare 1.2 . has anyone encountered this? what is the workaround
for this?

Thanks

Joachim