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

Error: Failed to parseField countryCode #46

Open
R-D-P opened this issue Nov 13, 2021 · 8 comments
Open

Error: Failed to parseField countryCode #46

R-D-P opened this issue Nov 13, 2021 · 8 comments

Comments

@R-D-P
Copy link

R-D-P commented Nov 13, 2021

Getting this error in the response.
There is also a soap message "soapMessage: '<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">soap:Bodysoap:Faultsoap:ServerThe given SOAPAction urn:ec.europa.eu:taxud:vies:services:checkVat/checkVat does not match an operation.</soap:Fault></soap:Body></soap:Envelope>'"

@R-D-P
Copy link
Author

R-D-P commented Nov 13, 2021

I am using version "validate-vat": "^0.8.0"

@Retosi
Copy link

Retosi commented Nov 17, 2021

Are you sure, that you updated the package after changing the version to 0.8.0? I've gotten the same error recently and manually updated to 0.8 and it's working fine now. It got fixed in the .7 update.

After changing the package.json to the correct version, run npm i validate-vat -s again

@herkyl
Copy link

herkyl commented Jul 16, 2022

Any fixes for this? Getting the same error after upgrading to 0.8.0

@callezenwaka
Copy link

Any fix for this issue, still getting it with version 0.8.0.

@Retosi
Copy link

Retosi commented Sep 20, 2022

I have gotten the issue again later on with 0.8.0, we were able to upgrade to the typescript version of validate-vat (validate-vat-ts). So if you are using it in a Typescript project, I'd recommend changing. We did not experience any issues since

@callezenwaka
Copy link

Thanks @Retosi for the suggestion, unfortunately, we are not using typescript.

@thebillg
Copy link
Contributor

try 0.9.0

@callezenwaka
Copy link

callezenwaka commented Sep 28, 2022

Thanks @thebillg, we have bumped it up to 0.9.0. Working perfectly now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants