-
Notifications
You must be signed in to change notification settings - Fork 34
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
Error with search.js (v1.1.0): 'Client ID is invalid' #22
Comments
I'm not sure if this will be helpful but when I forked the project and tried to use search.js, I had to change the following line in store.tsx. They changed this in the recent version. I'm not sure if I got the same error you did, but that was the only issue I had about two months ago.
|
Thank you for your help and solution! Your advice was very useful. With the change, I managed to fix my problem. I really appreciate your expertise. Thanks again! |
Thanks for raising this; I've created an internal ticket, MSRCH-4621, to address the issue. |
The fix is going in with other v2 feature set, and should be merged soon. https://github.com/adobe/storefront-product-listing-page/blob/feature/v2/src/context/store.tsx#L77 |
I have made the updates as mentioned in the posts but I still get the same issue, any ideas? @allforcode @MichaelHeinzman |
Actual Behaviour
I followed the instructions provided in the README to build search.js version 1.1.0 for a Magento website. However, when I integrated the file into the website, I encountered an error stating 'Client ID is invalid.' from the request
https://catalog-service-sandbox.adobe.io/graphql
Interestingly, I noticed that there is no issue when using the version v1.0.4, which comes from the URL https://plp-widgets-ui.magento-ds.com/v1/search.js.
Could there be issues in v1.1.0 that are not present in v1.0.4?
Expected Behaviour
Search.js should function without errors and provide the expected search functionality on the website.
Steps to Reproduce
npm run build
.Platform and Version
Adobe Magento Commerce ver. 2.4.7
The text was updated successfully, but these errors were encountered: