Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I'm not sure if there's a simpler test...
However, to see this defect with the sample application provided:
1. Start the application
2. Tap the 'Move' button on the first item
This will move the item to the listview in the other tab
3. Navigate to the 'Delivered' tab.
The item '0' should be there.
4. Tab the item.
It should be highlighted in blue
5. Go back to the 'Delivered' tab
6. Tab the 'Move' button on the first item
7. Navigate to the 'Delivered' tab
The second item should be in the ListView
The second item is NOT in the ListView
Tap the empty space of the ListView a couple of times...
The item will appear!
It's worth noting that this bug has existed since 1.4.0 I think.
I'm stuck on 1.3.5 and haven't been able to upgrade.
Created attachment 11148 [details]
Behavior is as described. Could be user error however to my eye the code looks reasonable. I'd expect it to work.
On master, I can now click on Move for item one, verify a new row appeared in delivered, click on move for item two, and verify a new row appeared in delivered. This is the expected behavior so apparently another fix on master also resolved this issue. Please wait for the next release before verifying this fix.
I don't see this issue in 2.3.3.-pre3. Can it be closed?