-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
GraphQl products query returns error: GetAttributeValueComposite::execute(): Argument #3 ($value) must be of type string, null given #38884
Comments
Hi @zakdma. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Delta. Thank you for working on this issue.
|
Just so you know, the problem is not only with null/string. There is also a problem with any other value type other than string. For example if value is int there will be the same error. |
Hi @zakdma , Verified the issue on 2.4-develop and we are not able to reproduce this issue. Steps to reproduce:- 1.Install vanilla Magento created attribute the values added to default attribute set product created and value saved to option 1 product edited value emptied and saved no error Please refer the attached screenshots and let us know if we missed anything. |
Why am I getting this response? I did not report or comment on this. |
Hey @engcom-Delta Also please use OpenSearch as a search engine and reindex all indexes Regards. |
Hi @zakdma , Verified the issue on 2.4-develop and we are not able to reproduce this issue. Preconditions:- OpenSearch search engine configured and used by Magento Steps to reproduce:- 1.Install vanilla Magento Created new attribute added on default test attribute Created new product edited product Reindex all indexes Actual result: We are not getting internal server error Please refer the attached screenshots and let us know if we missed anything. |
Hey @engcom-Delta |
Can confirm that we've run into this exact same issue. I think it might be easiest to hit if you don't use any filters in the |
@magento give me 2.4-develop instance |
Hi @mattijv. Thank you for your request. I'm working on Magento instance for you. |
Hi @mattijv, here is your Magento Instance: https://a9e3443cace74767d676b31ac81cd65a.instances-prod.magento-community.engineering |
I was able to reproduce the issue (not the exact same steps, but it's the same underlying issue) in the dev instance provisioned above. Steps:
Here's the query used for copypaste convenience:
|
Hi @zakdma, Verified the issue on 2.4-develop and 2.4.7 and it is reproducible. Hence, Confirming the issue. Steps to reproduce:- 1.Install vanilla Magento created attribute attribute settings attribute added to default attribute set Created new product edited product reindexing Graphql result Exception log |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-12328 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-Delta. Thank you for verifying the issue. |
❌ You don't have permission to export this issue. |
Hey @engcom-Delta @mattijv
|
❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-12328 |
Preconditions and environment
Steps to reproduce
bin/magento ind:reind
Please make sure they all reindexed successfullyExpected result
There is list of products with the simple-null product in it.
There is no error
Actual result
There is error in response
Check exception.log and see error:
Additional information
Issue is because \Magento\EavGraphQl\Model\Output\Value\GetAttributeValueInterface::execute hase third paremeter $value of type string when null value received.
Note: Just so you know, the problem is not only with null/string. There is also a problem with any other value type other than string. For example if value is int there will be the same error.
I found the same issue when I added the quote address custom attribute with int type. When setting this attribute value using setShippingAddressesOnCart and retrieving the shipping address it also failed.
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: