Home/ Questions/Q 7718049
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T03:04:09+00:00

The following code crashes and burns and I don’t understand why: DateTime dt =

  • 0

The following code crashes and burns and I don’t understand why:

DateTime dt = new DateTime(1970,1,1,0,0,0,0, DateTimeKind.Utc);
double d = double.Parse("1332958778172");

Console.Write(dt.AddSeconds(d));

Can someone tell me what’s going on? I just can’t seem to be able to figure out why…

EDIT

This value comes back from the Salesforce REST API and from what I understand it’s a Unix epoch time stamp. “The time of token issue, represented as the number of seconds since the Unix epoch (00:00:00 UTC on 1 January 1970).”

SOLUTION

Salesforce REST API is in fact sending milliseconds back for the issued_at field when performing the OAuth request when they say they’re sending seconds…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As others have said, the problem is that the value is too large.

    Having looked over it, I believe it represents milliseconds since the Unix epoch, not seconds so you want:

    DateTime dt = new DateTime(1970,1,1,0,0,0,0, DateTimeKind.Utc);
double d = double.Parse("1332958778172");  // Or avoid parsing if possible :)
Console.Write(dt.AddMilliseconds(d));

    Either that, or divide by 1000 before calling AddSeconds – but obviously that will lose data.

    • 0