Store view switcher is wrong , when each store views have different url.

[Taku-Yamashita]

Preconditions (*)

1. Magento 2.3.1
2. using 2 store views and those views have different url (en.magento.local & jp.magento.local)

Steps to reproduce (*)

1. Click a target store view on language switcher.
2. successfully switch to target store view.
3. but will be displayed below error.
   The store that was requested wasn't found. Verify the store and try again.

Expected result (*)

1. Switch to target store view.
2. no errors are displayed.

Actual result (*)

1. Switch to target store view.
2. below error is displayed.
   The store that was requested wasn't found. Verify the store and try again.

[m2-assistant]

Hi @Taku-Yamashita. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@Taku-Yamashita do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. 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-18256 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.

[gtlt]

linking possible similar issue : #22966

[magento-engcom-team]

Hi @Taku-Yamashita. Thank you for your report.
The issue has been fixed in #26548 by @TobiasCodeNull in 2.4-develop branch
Related commit(s):

• 346e544911827c379bdfed10f29ea40889d57078
• 392bd3b899cd26d5d329eaa0ab7e7a1b91125c4b
• 0cbc5b641efdee01fa2bd4222c2cc313d3846198
• 420fa1c739a2b568a115defdc58509976241464d
• 1375b5356aae59924f0e8f70b1970e8b85877e19
• 9cad4dcf942f1be3f704a16293116458c7b837fe
• 602419572902c06ed81a58080391207304c32760
• ee97fb5c647ce047d98d2a5554c67540df3fd7cf
• 689093a20a8d4226c2ca74c039a8136b7604887e
• 4708394d867aa235d51489f0e12b9705f081b9db
• 597bb18bc0faba8b0e67a499749c15785a23da16
• 0fcb6a0c06cbcbf733da284bb94b85a5e1ea1f16

The fix will be available with the upcoming 2.4.0 release.