Bug 29513 - When using Microsoft Band SDK Preview, the SendMessageTaskAsync method ignored the date specified
Summary: When using Microsoft Band SDK Preview, the SendMessageTaskAsync method ignore...
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: N/A
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Matthew Leibowitz
Depends on:
Reported: 2015-04-29 03:54 UTC by John Hardman
Modified: 2015-04-29 08:30 UTC (History)
1 user (show)

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

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 John Hardman 2015-04-29 03:54:04 UTC
Using the following piece of code from Xamarin Android code, using the Microsoft Band SDK Preview, the DateTime specified seems to be ignored, with what appears to be default date/time information being displayed on the band instead of the value specified.
            await client.NotificationManager.SendMessageTaskAsync(
                new DateTime(2015,04,24,17,57,30),    // or alternatively using DateTime.Now,
                args.ShowDialog ? MessageFlags.ShowDialog : MessageFlags.None);

It would appear that not only is the fourth argument ignored, but it may also be the wrong type. It has been reported in the forum that the underlying Microsoft method expects a DateTimeOffset rather than a DateTime.
Comment 1 Matthew Leibowitz 2015-04-29 08:30:44 UTC
Fixed in the next release: version 1.3.4

This issue was that the .NET DateTime time component was not carried across to the Java Date type.