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:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

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.

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.

Hi @avstaylime ,

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

Thanks,

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

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.

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"
   
2. Enter the same configuration in magento instance.
   
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.
   
   Observe error displays.

Thanks.

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.

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

✅ 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.

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.

@magento i'm working on this

This PR works for me. Thanks

@engcom-Delta This issue fixed by adobe team. please check and close this issue

@Mohamed-Asar Thanks for your Contribution!!.

Hi @avstaylime ,

As I can see this issue got fixed in the scope of the internal Jira ticket ACP2E-3340 by the internal team
Related commits: https://github.com/search?q=repo%3Amagento%2Fmagento2+ACP2E-3340&type=commits

Based on the Jira ticket, the target version is 2.4.8-beta2.

Thanks