Bug 13184 - [MonoTouch.Dialog] TimeElement off by nine minutes
Summary: [MonoTouch.Dialog] TimeElement off by nine minutes
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.9.3.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-07-11 14:55 UTC by Pierce Boggan [MSFT]
Modified: 2017-03-23 18:27 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Test case: shows working + nonworking TimeElement (14.02 KB, application/zip)
2013-07-11 14:55 UTC, Pierce Boggan [MSFT]

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Pierce Boggan [MSFT] 2013-07-11 14:55:41 UTC
Created attachment 4321 [details]
Test case: shows working + nonworking TimeElement

Description of Issue: When working with the TimeElement, and a UIDatePicker. The DatePicker will show nine minutes later than the DateValue returned. Setting the backing DateTime of the TimeElement to an instantiated but unset DateTime causes the datePicker to display 9 minutes ahead of what it actually returns. However, if you set the DateTime to a value before using it with the TimeElement, the UIDatePicker displays great! 
Testcase: Attached.

Version Information:
=== Xamarin Studio ===

Version 4.1.5 (build 2)
Installation UUID: dbb93e30-b525-4632-8fdd-511fbc37c560
	Mono 3.0.12 ((no/d6c5db8)
	GTK 2.24.18
	GTK# (
	Package version: 300120000

=== Apple Developer Tools ===

Xcode 4.6.3 (2068)
Build 4H1503

=== Xamarin.Mac ===

Xamarin.Mac: 1.4.22

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 7f9e851
Build date: 2013-10-07 12:10:26-0400

=== Xamarin.Android ===

Version: 4.7.11 (Business Edition)
Android SDK: /Users/pierceboggan/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0   (API level 14)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
Java SDK: /usr
java version "1.6.0_51"
Java(TM) SE Runtime Environment (build 1.6.0_51-b11-457-11M4509)
Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01-457, mixed mode)

=== Build Information ===

Release ID: 401050002
Git revision: c83a26fbfd92eb87016eca2fa655dbd996f9a899
Build date: 2013-07-09 20:37:20+0000
Xamarin addins: 6b029b21a6c1ee965bdc441cdf9e017ac75e7295

=== Operating System ===

Mac OS X 10.9.0
Darwin Pierces-Amazing-Macbook-Pro.local 13.0.0 Darwin Kernel Version 13.0.0
    Tue Jul  2 15:57:48 PDT 2013
    root:xnu-2422.1.35~2/RELEASE_X86_64 x86_64
Comment 4 Manuel de la Peña [MSFT] 2017-03-23 18:27:35 UTC
As per a conversation with Pierce, closing this since MonoTouch.Dialog isn't actively maintained anymore and nothing will be fixed (even if issues do exist).