[Bug]: `lowestRate()` returns rates for `USPS` even though requested only for `USPSReturns`
See original GitHub issueSoftware Version
3.8.1, however the problem appears to be in the latest version too
Language Version
Node v14.21.1
Operating System
unrelated
What happened?
- Create new
Shipment
- Get lowest rate for
USPSReturns
(shipment.lowestRate(['USPSReturns'])
) - Method returned the lowest rate but for the
USPS
carrier
What was expected?
It should return the lowest rate for USPSReturns
carrier.
Sample Code
const EasyPost = require('@easypost/api');
const client = new EasyPost(credentials);
const shipment = new client.Shipment(parcelData);
await shipment.save();
const lowestRate = shipment.lowestRate(['USPSReturns']);
Relevant logs
No response
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Returns Made Easy - USPS
Returns are easy with USPS®. Just print your own shipping label with postage and then schedule a Package Pickup.
Read more >Return to Sender Mail - FAQ | USPS
Mail with insufficient information or mail that has insufficient postage is rejected and returned to the sender with the endorsement “Return ...
Read more >Customer Returns - Label Services and Package Return Options
Manage package returns and merchandise returns with preprinted return labels, scan-based postage charges, and options for speed, economy, insurance, ...
Read more >Parcel Return Service (PRS) - FAQ | USPS
If a Parcel Return Services (PRS) label is used on a package, the Postal Service will charge the merchant the appropriate PRS price,...
Read more >Request a USPS Refund: Domestic
Learn how to request a refund for USPS service fees and postage for mail sent within the US. See what services you can...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Justintime50 turns out… it was all over a deployment issue. I’m sorry for taking your time. There’s nothing to be resolved. Thank you!
@Justintime50 dang, you’re right. I’m not sure how I missed that… I’ll reach out to our dev to get the details of the shipment that supposedly failed.
Thank you!