GraphQL OPTIONS request fails with storefront combability module

[sashas777]

Preconditions and environment

• Magento version 2.4.7-p3
• Install module adobe-commerce/storefront-compatibility

composer require adobe-commerce/storefront-compatibility

• Apply Patch ACSD-63325

Steps to reproduce

Run from bash following CURL:

curl -i -X OPTIONS http://commerce.local/graphql

Expected result

The response code is 200 for the request.

Actual result

A 500 internal server error occurs:

{"errors":[{"message":"Syntax Error: Unexpected <EOF>","locations":[{"line":1,"column":1}],"extensions":{"file":"\/var\/www\/magento\/vendor\/webonyx\/graphql-php\/src\/Language\/Parser.php","line":439}}]}

Additional information

The module adobe-commerce/storefront-compatibility has an around plugin vendor/adobe-commerce/module-authorization-storefront-compatibility/Plugin/Controller/GraphQlPlugin.php that need to be patched similar way that the patch ACSD-63325 applies to vendor/magento/module-graph-ql/Controller/GraphQl.php

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”.

[m2-assistant]

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

[yogesh-valiya]

@magento-engcom-team give me 2.4.7 instance

[yogesh-valiya]

@magento give me 2.4.7 instance

[m2-assistant]

Hi @engcom-November. 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.

[engcom-November]

Hello @sashas777 ,

We appreciate your cooperation and reporting.

We attempted to replicate the issue in the most recent instance, 2.4.7-p4, and it is reproducible. Please refer to the screenshots that are attached.

and we have not installed store compatibility, even though we are having this issue.

We'll be working on it and keeping you updated.

Thus, the issue has been confirmed.

Thank you.

[github-jira-sync-bot]

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

[m2-assistant]

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