Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.2.0
-
Component/s: None
-
Labels:None
Description
One client encountered an error when validating an approved token, since the api request to fetch ledgers resulted in an error like the following:
[2021-10-04T19:43:39.998692+00:00] general.ERROR: BITPAY-LEDGER-GET: Failed to retrieve ledger-> failed to serialize Ledger object : GET failed : Guzzle\/BadResponseException : Server error: `GET https://bitpay.com/ledgers?token=6YZajLf5hJ2yMd7ttyer6r6qY3tM3a1KmJysmknSdKcMg resulted in a 500 Internal Server Error` response: {"error":"No ledgers for account"}
This happened even though there were ledgers assigned to the user. The subscription api call seems to be more reliable.
Change:
$ledgers = $bitpay->getLedgers();
To
$subscriptions = $bitpay->getSubscriptions();
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Issue Type | Task [ 3 ] | Improvement [ 4 ] |
| Story Points | 2 |
| Sprint | 5.3.0 Sprint 2 [ 139 ] |
| Rank | Ranked lower |
| Assignee | Abdy Franco [ abdy ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 14 minutes [ 840 ] | |
| Worklog Id | 15331 [ 15331 ] |
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | In Review [ 5 ] | Closed [ 6 ] |
