-
Notifications
You must be signed in to change notification settings - Fork 20
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
Uncaught Error: Interface 'Magento\QuoteGraphQl\Model\Cart\Payment\AdditionalDataProviderInterface' #15
Comments
The error shows that the Braintree GraphQL module is still there, but in this repository it is actually removed: https://github.com/yireo/magento2-replace-graphql/blob/magento-2.4.0/composer.json#L8 Could it be that you are using the wrong version of this package? |
this is part of the composer.json:
that's really wierd cause yes it seems the module it's still there but I've also removed the vendor folder completely and re-done a "composer install" |
Could you try with removing the |
I removed it when reinstalling, super weird |
Just adding these replacements using So the issue is solved? |
also removing the composer.lock and re-installing I get the same error (on php7.4). I solved copying/pasting the replace lines but I had to "keep" the quote-graphql, customer-graphql, graphql |
Thanks. I've been trying this out again, but in my case, with a vanilla Magento 2.4.0 and PHP 7.4 and the mentioned packages, it simply works. This is also tested for in the GitHub Actions of this workspace. It almost seems if there are additional packages installed in your environment that are not part of my regular 2.4 installation. Perhaps because of Marketplace extensions you have installed. Either way, by inspecting the output of |
I'm going to close this due to inactivity. Feel free to reopen when this is still relevant. |
Hi guys, on a vanilla M2.4.0 + your replace-graphql repo I'm getting this error while lunching a setup:di:compile
did you ever encounter something like this?
thanks a lot!
The text was updated successfully, but these errors were encountered: