Tracking information is currently not available.

[fvlasie]

Preconditions and environment

• Magento version: 2.4.6-p3 I have set up USPS and UPS in Delivery Methods. Both are working to retrieve prices. I am also using ShipStation to print labels and ShipStation sends the tracking number back to Magento.

Steps to reproduce

Open an order that has shipped under Sales>Orders In the Shipping section click the link for "Track this shipment" after clicking "view" The tracking pop-up will show the error "Tracking information is currently not available".

This same error shows regardless of shipping vendor, in my case USPS and UPS.

Expected result

The tracking information should show.

Actual result

Tracking information is currently not available.

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] 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”.

[m2-assistant[bot]]

Hi @fvlasie. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[m2-assistant[bot]]

Hi @engcom-Bravo. 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: :point_down:

• [ ] 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.

[m2-assistant[bot]]

Hi @engcom-Dash. 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: :point_down:

• 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering Admin access: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering/admin_b5e7 Login: 48252078 Password: 95177df0e3ac

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering Admin access: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering/admin_81ef Login: c880ada8 Password: 9041c575d15f

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering Admin access: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering/admin_e688 Login: 531909e4 Password: 9d58c2f5173b

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering Admin access: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering/admin_2ab6 Login: 708362e3 Password: e83227ed47c3

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering Admin access: https://5c3b6bb39f5f04b9d23ffaab0ec768c3.instances-prod.magento-community.engineering/admin_7e1a Login: 55b19525 Password: e568fce92cfd

[engcom-Dash]

Hi @fvlasie

Thanks for reporting and collaboration.

Verified the issue on magento 2.4 developer instance and the issue is reproducible. Tested with both USPS and UPS delivery methods and shipped the order. When clicked on the track the shipment link we are getting "Tracking information is currently not available". Please refer the attached screenshots.

[github-jira-sync-bot]

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

[m2-assistant[bot]]

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

[Kishorchhugani]

Any Updates regarding this issue ? I am having same issue on Magento 246p1

[rydemods]

Also having this issue, looking for a fix 2.4.6-p3

[tkawai21]

I'm also having this issue on v2.4.5-p1 and v2.4.5-p7.

On v2.4.5-p1, if I keep reloading the tracking popup, it'll eventually show the tracking details.

[engcom-Bravo]

Hi @fvlasie,

We tested the issue on 2.4-develop by enabling the UPS shipping method and creating a shipping label to obtain the tracking number for sending out tracking information to the ordered customer. After sending the tracking information to the customer, upon clicking "Track This Shipment" in the ordered shipment section, we were able to see a pop-up with all the tracking information. Thus, the issue was not reproducible. We have also attached a screen recording for reference.

https://github.com/magento/magento2/assets/51680745/afba3fb8-1964-411d-b7bc-293865389c04

Thanks.

[DannyDaemonic]

@engcom-Bravo For our install and in the screenshots provided earlier, the issue was with USPS. UPS works fine here as well. Could you please try this with USPS?

[tkawai21]

@engcom-Bravo I've noticed it happening with UPS and FedEx. Here is a screencap recording of the issue with FedEx. In it, I'm repeatedly refreshing the popup and it eventually shows the details around the 0:22 mark.

[engcom-Bravo]

Hi @tkawai21,

As we have already mentioned here, we have verified the issue on 2.4 develop for UPS delivery method and the issue was not reproducible. Also we have attached the screen recording for the reference.please once reverify from your end.

https://github.com/magento/magento2/assets/51680745/d541cb88-3e39-4899-a954-602518b80b5d

Thanks.

[tkawai21]

I'm definitely still having the issue on my end. But as a workaround, I'm testing out this extension: https://github.com/karliuka/m2.TrackingLink

It's looking pretty promising and we modified it so it'll also replace the tracking details with the direct Carrier's tracking link when viewing the tracking from the frontend or admin.