Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The store that was requested wasn't found #39770

Open
5 tasks
coresh opened this issue Mar 27, 2025 · 5 comments
Open
5 tasks

The store that was requested wasn't found #39770

coresh opened this issue Mar 27, 2025 · 5 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.8-beta2 Indicates original Magento version for the Issue report.

Comments

@coresh
Copy link

coresh commented Mar 27, 2025

Preconditions and environment

  • Magento version: 2.4.7-p4, 2.4.8-beta2
  • php version: 8.3

Case: Core config data value for the path: 'web/url/use_store' === 1

select * from core_config_data where path='web/url/use_store';
+-----------+---------+----------+-------------------+-------+---------------------+
| config_id | scope   | scope_id | path              | value | updated_at          |
+-----------+---------+----------+-------------------+-------+---------------------+
|       523 | default |        0 | web/url/use_store | 1     | 2024-08-29 20:49:29 |
+-----------+---------+----------+-------------------+-------+---------------------+

Steps to reproduce

php.ini:

xdebug.mode=develop,trace

The issue provided by the request:

curl 'https://your-magento-test-host.com/graphql' -H 'accept: */*' -H 'accept-language: en-US,en;q=0.9' -H 'authorization;' -H 'cache-control: no-cache' -H 'content-type: application/json' -b 'SID=94638c7c90fa603674e1df25068d13d6; _ga=GA1.1.1738941708.1742491653; pwaProMore=1; cookie_accepted=true; cf_clearance=FwzcQkb_y5TxCmAatAQ22oOun9jzGow1XWdB8QA7VL0-1742536421-1.2.1.1-pQ_1vRuHXNR.t34JcS9EFcH.k1B54Hmkjaom_W.AmIcaCP1ycv39jwrMDu8RDR3rmr58YasLwU4ZURrJRVma7JsmhMljnCeNJ7oIeCYQbllqJSm43aQygaghKXQQ11Z_AgpFKtcVfz08AKDXYvyXzLVAmNxZW5pdlKu4wLe_kvI3Ss3GFDgOkLpPL1iwgzg_5WWCzFVyxD8mAvOvNzrSG6GqwrYnoI7wEz7JRRYCJm1N.UWw8YxFop4RqykGFQhLkmsyQVu9up.7RYaWoZAKvi_kHwbv_XMhGYybPe6se7eLdtoGBoGRHrjV7lprVwsKyek9WKgj2k0NzUFCbr6ByFRLZSmyCglFkfXgp_Wd4_o; _ga_LWFKYRLFVB=GS1.1.1742536422.5.0.1742536422.0.0.0' -H 'origin: https://your-magento-test-host.com' -H 'pragma: no-cache' -H 'priority: u=1, i' -H 'referer: https://your-magento-test-host.com/en_us/' -H 'sec-ch-ua: "Not:A-Brand";v="24", "Chromium";v="134"' -H 'sec-ch-ua-mobile: ?0' -H 'sec-ch-ua-platform: "Linux"' -H 'sec-fetch-dest: empty' -H 'sec-fetch-mode: cors' -H 'sec-fetch-site: same-origin' -H 'store: en_us' -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36' -H 'x-magento-cache-id: b665ee02f24c915afc32f00f3697beb351eea255490f62b3e93dbdaf4ba1bff6' --data-raw '{"operationName":"createCart","variables":{},"query":"mutation createCart {\n  cartId: createEmptyCart\n}\n"}';

Expected result

{"data":{"cartId":"vVujuoM9XmEGzeootUTWt7adbJPlHUQ5"}}

Actual result

'{"operationName":"createCart","variables":{},"query":"mutation createCart {\n  cartId: createEmptyCart\n}\n"}';

Additional information

Magento\Framework\Exception\NoSuchEntityException

Magento\Framework\Exception\NoSuchEntityException: The store that was requested wasn't found. Verify the store and try again.  in vendor/magento/module-store/Model/StoreRepository.php on line 75

Call Stack:
    0.0001     507288   1. {main}() pub/index.php:0
    0.0110    2907496   2. Magento\Framework\App\Bootstrap->run($application = class Magento\Framework\App\Http { ... }) pub/index.php:35
    0.0111    2919104   3. Magento\Framework\App\Http->launch() vendor/magento/framework/App/Bootstrap.php:264
    0.0111    2919104   4. Magento\Framework\App\Request\Http->getFrontName() vendor/magento/framework/App/Http.php:111
    0.0111    2919104   5. Magento\Framework\App\Request\Http->getPathInfo() vendor/magento/framework/App/Request/Http.php:219
    0.0111    2919104   6. Magento\Framework\App\Request\Http->getOriginalPathInfo() vendor/magento/framework/App/Request/Http.php:169
    0.0111    2919144   7. Magento\Backend\App\Request\PathInfoProcessor\Proxy->process($request = class Magento\Framework\App\Request\Http { ... }, $pathInfo = '/graphql') vendor/magento/framework/App/Request/Http.php:154
    0.0121    2927000   8. Magento\Backend\App\Request\PathInfoProcessor->process($request = class Magento\Framework\App\Request\Http { ... }, $pathInfo = '/graphql') generated/code/Magento/Backend/App/Request/PathInfoProcessor/Proxy.php:105
    0.0140    3653080   9. Magento\Store\App\Request\PathInfoProcessor->process($request = class Magento\Framework\App\Request\Http { ... }, $pathInfo = '/graphql') vendor/magento/module-backend/App/Request/PathInfoProcessor.php:55
    0.0140    3653080  10. Magento\Store\App\Request\StorePathInfoValidator->getValidStoreCode($request = class Magento\Framework\App\Request\Http { ... }, $pathInfo = '/graphql') vendor/magento/module-store/App/Request/PathInfoProcessor.php:42
    0.0143    3818928  11. Magento\Store\Model\StoreRepository->getActiveStoreByCode($code = 'graphql') vendor/magento/module-store/App/Request/StorePathInfoValidator.php:99
    0.0143    3818928  12. Magento\Store\Model\StoreRepository->get($code = 'graphql') vendor/magento/module-store/Model/StoreRepository.php:89

Release note

No response

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.
  • 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”.
Copy link

m2-assistant bot commented Mar 27, 2025

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


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.

@engcom-Bravo engcom-Bravo self-assigned this Mar 27, 2025
Copy link

m2-assistant bot commented Mar 27, 2025

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

Sorry, something went wrong.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.8-beta2 Indicates original Magento version for the Issue report. label Mar 27, 2025
@engcom-Delta
Copy link
Contributor

Hi @coresh ,

Thanks for your reporting and collaboration.
We have tried to reproduce the issue in magento2.4.8-beta2 instance and we are not able to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce :

  1. Install magento2.4.8-beta2 instance
  2. Set Core config data value for the path: 'web/url/use_store' === 1

Image
3. php.ini:
xdebug.mode=develop,trace

Image
4. Run GraphQL - Observe error displays when we do not have any customer registered
Exception Log -
[2025-04-01T14:21:04.702380+00:00] main.ERROR: No such entity with customerId = 1

GraphQL (1:12)
1: mutation { createEmptyCart }
^
{"exception":"[object] (GraphQL\Error\Error(code: 0): No such entity with customerId = 1 at C:\xampp8.2php\htdocs\magento2.4.8-beta2\vendor\webonyx\graphql-php\src\Error\Error.php:171)
[previous exception] [object] (Magento\Framework\Exception\NoSuchEntityException(code: 0): No such entity with customerId = 1 at C:\xampp8.2php\htdocs\magento2.4.8-beta2\vendor\magento\framework\Exception\NoSuchEntityException.php:50)"} []

  1. Create a customer in frontend or admin.
  2. Run GraphQL again. Observe cartId is generating as expected.

Image

Kindly recheck the issue and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

@engcom-Delta engcom-Delta added the Issue: needs update Additional information is require, waiting for response label Apr 1, 2025
Copy link

m2-assistant bot commented Apr 1, 2025

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.

Sorry, something went wrong.

@coresh
Copy link
Author

coresh commented Apr 1, 2025

Hi, @engcom-Delta

Re: "Kindly recheck the issue and elaborate the steps to reproduce if the issue is still reproducible.":
Let's re-checking and monitoring...

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.8-beta2 Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

3 participants