[BUG]: Guam is both a state of the US and a country.

[damienwebdev]

Preconditions and environment

• Magento version: v2.4.6-p*
• Anything else that would help a developer reproduce the bug

In the Magento database, Guam is listed both as a country on its own as well as a state of the US.

Country: https://github.com/magento/magento2/blob/03621bbcd75cbac4ffa8266a51aa2606980f4830/app/code/Magento/Directory/Setup/Patch/Data/InitializeDirectoryData.php#L145

State: https://github.com/magento/magento2/blob/03621bbcd75cbac4ffa8266a51aa2606980f4830/app/code/Magento/Directory/Setup/Patch/Data/InitializeDirectoryData.php#L332

However, only the "state" Guam works with USPS when calculating rates.

Additionally, Guam is considered a country in GraphQl here.

Steps to reproduce

1. Enable USPS rate calculation
2. Set a Guam address on your cart with Guam as a country
3. Calculate rates
4. See no rates available.
5. Set a Guam address on your cart with United states as a country and Guam as a state.
6. See rates.

Expected result

I expect to be able to set my Guam address on my cart without in one way that works.

Actual result

I sometimes get rates, other times I don't.

Additional information

Here is a related issue. https://github.com/magento/magento2/issues/35610

I suspect entirely removing Guam as a country is the appropriate method. Additionally, this mandates setup patches to migrate existing customers in Guam to the US on top of removing Guam as a country.

These are the approximate appropriate steps to take.

DELETE from directory_country where country_id = "GU";

-- Get region id
SELECT @guamRegion := `region_id` FROM directory_country_region where country_id = "US" and code = "GU";

UPDATE customer_address_entity SET country_id='US', region_id=@guamRegion where country_id = "GU";
UPDATE quote_address SET country_id='US', region_id=@guamRegion where country_id = "GU";
UPDATE sales_order_address SET country_id='US', region_id=@guamRegion where country_id = "GU";

Release note

Customers that live in Guam can now purchase items from Magento stores without grief.

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.
• [X] 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 @damienwebdev. 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-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://22d61490e580ec52e5ecd2b4fe8b3db7.instances-prod.magento-community.engineering Admin access: https://22d61490e580ec52e5ecd2b4fe8b3db7.instances-prod.magento-community.engineering/admin_aedd Login: 79e92bbb Password: 04105a6b01dc

[engcom-Dash]

Hi @damienwebdev

Thanks for reporting and collaboration.

Verified the issue on magento 2.4 dev instance but the issue is not reproducable.

We are seeing calculated shipping rates when the country is guam and when the country is US and state is guam.

Please refer the attached screenrecording.

https://github.com/magento/magento2/assets/60198592/7d7be1eb-0699-4472-a702-c7cb96a903ec

Please verify the issue in magento 2.4 dev instance and let us know if we missed anything and if you are still facing the issue.

[engcom-Dash]

Hi @damienwebdev

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks