[Issue] Fix wrong format error DHL shipping label

[m2-assistant]

This issue is automatically created based on existing pull request: #31021: Fix wrong format error DHL shipping label

---

Fix "The response is in wrong format." error while generating dhl shipping label. When product name has unicode characters substr() is sending � in causing erros dhl syntax errors.

Description (*)

DHL shipping.log produces error "Error in parsing request XML:The element type "PieceContents" must be terminated by the matching end-tag "</PieceContents>"."

This is caused in our use case by substr() not supporting multibyte characters in product name.

Preconditions

1. Magento 2.4-develop
2. Magento DHL settings and Store Settings set for USA address
3. A Customer with a valid United Kingdom address

Steps to reproduce (*)

1. create a product with product name "Φυστίκι Ψημένο με Αλάτι Συσκευασία"
2. place an order with dhl shipping method (having debug mode will help trace dhl error response)
3. try to ship order with "create shipping label" checkbox checked
4. while requesting label creation you get "The response is in wrong format."

Expected result

Shipping Label should be created

Actual Result

"The response format is wrong" error message appears

Note from Engcom ❗

We are able to get the error message with a product named Product

[m2-assistant]

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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-39723 were created

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.

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #31021 by @vpsnak in 2.4-develop branch
Related commit(s):

• ba1a3393e5b09a141a2a06e11d15dad91a8e041c
• a8c72b00d7d30a60499e0aea085fade9df480b82
• 0bdf6ab48c804ca4c23933b34b27300498b0d4bb
• 93c09b3372be8f9486490faa36914213f6a36798
• 923091e44e3660d9ddba83c24a3828c6ae6f14d7
• 72574a8e5e6257f52aecb21df4bcd1f3990f31c9
• a3536cb91c494a8c6c4cfb2c1d61f222be64bbf1
• f5ed249e645a73309438fae73f237dbc1cc3aef8
• ca76fdbe7acff4b477570bd570bba976b66f0af7
• b0e5d5a25911267351ed26618d1b450f23eb950d
• 22f4f8eb70392cc158899f657f125d9e5dab6512
• f20cf5820f19013a49504c81450b840f4fa3e720
• cff6a6fd3622df94ec0e9760d6283ec01d66af80
• ff979509acc574f3f95a3cdd19c685eba7645a49
• 8749553fca0ce2b626bd45d4af2f72815a46c458
• 673bd22a3ebb027999e0773bb4437e925a45e5a7

The fix will be available with the upcoming 2.4.3 release.