Hi @ShapesGraphicStudio. 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.

• 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

  - 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 @ShapesGraphicStudio ,

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

Steps to reproduce

1. Place an order with more than 35 characters as shipping address and fedex shipping method.
2. Create shipping label.
3. Observe user is unable to create shipping label and user receives error as shipping address is more than 35 characters.
   

Thanks.

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

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

Hello,
I don't understand why this is marked as feature request instaed of issue to fix.
This is blocking the creation of some shipping labels.
I notices this has been discusted also here in issue #39072:

"the API request are being sent to FedEx as [streetLine1 . streetLine2], but it should be [streetLine1, streetLine2]"

@ShapesGraphicStudio The issue that you have linked has a pull request to fix the issue unless I am missing something...

Hello,

We have asked our FEDEX contact and each lign must not exceed 35 characters INCLUDING SPACE. Thats explains that each time we think we are under 35 characters, we are usually at more.

Do you know how could we "stop" the consumer to write more than 35 characters ?
Maybe activate an automatic message at 35 characters "Address too long, please use the lines below"