Skip to content
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 integration doesn't support Track API being a separate Project in FedEx account #38859

Open
1 of 5 tasks
avstaylime opened this issue Jun 21, 2024 · 12 comments · May be fixed by #39365
Open
1 of 5 tasks

Fedex integration doesn't support Track API being a separate Project in FedEx account #38859

avstaylime opened this issue Jun 21, 2024 · 12 comments · May be fixed by #39365
Assignees
Labels
Area: Shipping Component: Fedex Component: Shipping Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: PR in progress Reported on 2.4.7 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@avstaylime
Copy link

Preconditions and environment

  • Magento 2.4.7
  • New FedEx account (created after Oct '23) that offers to choose between Ship, Rate & Other APIs and Track API

Steps to reproduce

  1. Enable FedEx shipping method by entering API credentials from a FedEx Project of a type Ship, Rate & Other APIs.
  2. Place an order and enter enter a FedEx tracking number when creating a shipment.
  3. Click Track Order to view tracking details.

Expected result

Tracking details listed

Actual result

Tracking information is currently not available. Please contact us for more information or email us at [email protected]

Additional information

select-project It is not possible to select both `Ship, Rate & Other APIs` and `Track API` for a FedEx Project. So there should be additional config for Track API under the FedEx settings in the Magento Admin.

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Copy link

m2-assistant bot commented Jun 21, 2024

Hi @avstaylime. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Copy link

m2-assistant bot commented Jun 21, 2024

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Delta engcom-Delta added the Reported on 2.4.7 Indicates original Magento version for the Issue report. label Jun 21, 2024
@engcom-Delta
Copy link
Contributor

Hi @avstaylime ,

We are putting this issue on hold as of now , as we need some PO confirmation on this.

Thanks,

@NeoM-dev
Copy link

Any update on fix? Having same issue tested everything many times.

@Robax-CSE
Copy link

Hi, I am experiencing the same issue with Magento 2 FedEx Integration.

I have created a project from the FedEx developer portal, but the Track API cannot be enabled on the same project as the Ship API, and the FedEx Magento 2 integration only allows one API Key in the configuration panel at the moment.

@engcom-Delta
Copy link
Contributor

engcom-Delta commented Aug 30, 2024

Hi @avstaylime ,

Thanks for your reporting and collaboration.
We have verified the issue in latest 2.4-develop instance and the issue is reproducible.
Kindly refer the screenshots.

Steps to reproduce -

  1. Create a project in Fedex for "Rate,Ship,Other"
    image
  2. Enter the same configuration in magento instance.
    image
  3. Save the configuration and Access frontend.
  4. Place order successfully with Fedex shipping method.
  5. Access Admin, Create invoice for respective order.
  6. Create shipment with tracking number.
  7. Access shipment and click on tracking number.
    image
    Observe error displays.

Thanks.

@engcom-Delta engcom-Delta added Component: Paypal Reported on 2.4.x Indicates original Magento version for the Issue report. Area: Shipping Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed and removed Issue: On Hold labels Aug 30, 2024
@github-jira-sync-bot github-jira-sync-bot removed the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Aug 30, 2024
@github-jira-sync-bot
Copy link

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

@engcom-Delta engcom-Delta added Reported on 2.4.7 Indicates original Magento version for the Issue report. Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed and removed Issue: ready for confirmation labels Aug 30, 2024
@github-jira-sync-bot github-jira-sync-bot removed the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Aug 30, 2024
@github-jira-sync-bot
Copy link

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

@engcom-Bravo engcom-Bravo added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch and removed Reported on 2.4.x Indicates original Magento version for the Issue report. labels Sep 2, 2024
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-12878 is successfully created for this GitHub issue.

Copy link

m2-assistant bot commented Sep 2, 2024

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@engcom-Bravo engcom-Bravo moved this from On Hold to Confirmed in Issue Confirmation and Triage Board Sep 2, 2024
@engcom-Hotel engcom-Hotel added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Sep 3, 2024
@chernenm chernenm added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. and removed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. labels Sep 17, 2024
@psol7
Copy link

psol7 commented Oct 2, 2024

Here is a work around solution for tracking Fedex shipment while the option of multi API credentials (1 for rates and 1 for tracking) is still not implemented in the Fedex modules in Magento.
Use the shipperHQ shipper-tracker, it allow to create manual link for tracking .
composer require shipperhq/module-shipping-tracker
or download at https://github.com/shipperhq/module-shipping-tracker
Then you can set a shipperHQ tracker using manual Url as below:
https://www.fedex.com/fedextrack/?trknbr=#TRACKNUM#
When customer click the link in the Magento tracking page it will resolve to the Fedex tracking info.

@Mohamed-Asar
Copy link
Contributor

@magento i'm working on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Shipping Component: Fedex Component: Shipping Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: PR in progress Reported on 2.4.7 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants