Collect: Range widget with appearance="picker" starts with an incorrect value

[mmarciniak90]

Software and hardware versions

Verified on Collect v1.11.0

Problem description

Range widget with appearance="picker" starts from incorrect value

Steps to reproduce the problem

1. User starts form with Range widget with appearance="picker"
2. User sees question

3. User sees 10 as a first value, next to 2
   

4. Values back to normal when user swipes
   

Expected behavior

First value is 1

Used form:
All widgets.xml.txt

[akshay-ap]

@opendatakit-bot claim

[getodk-bot]

Hello @akshay-ap, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 7 days. Are you still working on this issue?

If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 3 days.

If you've decided to work on something else, simply comment @opendatakit-bot unclaim so that someone else can claim it and continue from where you left off.

Thank you for your valuable contributions to Open Data Kit!

[akshay-ap]

I am working on it.

[akshay-ap]

I am trying to find the cause of such behavior.
In org.odk.collect.android.fragments.dialogs.NumberPickerDialog.onCreateDialog() method ,
I added Log.i("===: ","numberPicker.getValue() :" + String.valueOf(numberPicker.getValue())); for debugging.

The display value array is [10,9,8,7,6,5,4,3,2,1] stored in getArguments().getSerializable(DISPLAYED_VALUES)

The logged value 9 seems to be correct as it is expected 1 on the screen. But, the displayed value is 10 on the screen which is at index 0.
I am unable to find reason for such behavior.

[grzesiek2010]

It looks as if it's an Android bug. I was surprised because I tried to reproduce the issue and I used my Samsung Galaxy S4 with Android 5 (everything is ok) then I used Android 4.4. (everything is ok), Android 4.2 (everything is ok too)... Android 7 - yes I can reproduce the issue using that device, but I also can confirm that the list of displayed values is well prepared. And even if you select that wrong "10" the displayed value is 1 as expected so only the displayed in the NumberPicker value is wrong but the original one is ok.

What even weirder the problem takes place when we have a range 1-10 but everything is ok if I use 1-7 :smile: looks as if Android confuses 1 with 10 and 11 (I didn't check other numbers).

[akshay-ap]

If default value anything other than 1, everything works fine. Like if default is set to 2 the number picker shows values correctly.

[grzesiek2010]

If default value anything other than 1, everything works fine.

That's not true. I tested this form
range.xlsx and the same issue is when we have a range:
2-20 then 20 is displayed
2-22 then 22 is displayed etc.

Looks like a very strange bug in Android OS and there is nothing we can do here but we can keep this issue just to know about this bug.

[grzesiek2010]

@lognaturel @akshay-ap I created a sample project to confirm it's not our bug the project is here: https://github.com/grzesiek2010/NumberPickerBug and I also reported the issue here: https://issuetracker.google.com/issues/72690635

That's all we can do.

[akshay-ap]

@grzesiek2010 Thanks for correcting.

[getodk-bot]

Hello @akshay-ap, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 10 days.

You can reclaim this issue or claim any other issue by commenting @opendatakit-bot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

[lognaturel]

Nice report, @grzesiek2010. Let's close this since it's not a Collect issue. Please update here once you hear more from Google.