Closed SilverFire closed 6 years ago
Currently https://bitpay.com/invoices/%invoiceId% returns time with milliseconds as follows:
https://bitpay.com/invoices/%invoiceId%
'invoiceTime' => '1512559263104', 'expirationTime' => '1512560163104', 'currentTime' => '1512562237964',
Time assignation in Invoice.php on :477, :502, :527 is performed with assumption that timestamp is in seconds, that leads to obviously wrong DateTime object with date in far far future: 49901-02-15T09:51:44+01:00
Invoice.php
49901-02-15T09:51:44+01:00
See: https://3v4l.org/DUlIi
Fixed in v2.2.16
Currently
https://bitpay.com/invoices/%invoiceId%
returns time with milliseconds as follows:Time assignation in
Invoice.php
on :477, :502, :527 is performed with assumption that timestamp is in seconds, that leads to obviously wrong DateTime object with date in far far future:49901-02-15T09:51:44+01:00
See: https://3v4l.org/DUlIi