-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fedex REST API preferred currency issue #39765
Comments
Hi @mabaud. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-November. Thank you for working on this issue.
|
Hello @mabaud Thank you for your report and Collabration, We have gone through the description and we unable to find the this patch "ACSD-64325_2.4.7-p3.patch applied" could you please brief this and provide some more details it help us to reproduce the issue. Hence marking as "Needs Update" Thank you |
Hello, This is this patch: I assume it's the file for 2.4.7 related to the ACSD-61622 quality patch:
So you should apply the quality patch ACSD-61622 |
Preconditions and environment
Steps to reproduce
Expected result
Fedex rates
Actual result
An error occurred:
Can't convert a shipping cost from "USD-CAD" for FedEx carrier.
Additional information
We have this issue because in the fedex request the rateRequestType param is missing the "PREFERRED" value, and the preferredCurrency parameter is missing. This is causing fedex to respond rates in USD instead of CAD, and since we don't have currency rate USD/CAD in Magento, we are getting this error.
Note: we have this issue after applying that b22a00f (with the ACSD-64325_2.4.7-p3.patch)
We didn't have that issue with the SOAP API, Fedex was responding in CAD.
Here a quickfix I made (a patch file, you have to remove the .txt extension):
currency_issue.patch.txt
Workaround : pay for a currency converter service or manually set the currency rates USD/CAD every day :)
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: