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

fix The given SOAPAction checkVat does not match an operation. #105

Merged
merged 1 commit into from
Oct 29, 2021

Conversation

lubosch
Copy link
Contributor

@lubosch lubosch commented Oct 29, 2021

For some unknown reason this gem now throws this error: The given SOAPAction checkVat does not match an operation.

The reason for this is that savon inserts a SOAPaction header that brokes it. This workaround removes that header and the error is no longer risen. I didn't find any other workaround to remove this error. For more info look here:

Savon::SOAPRequest#configure_headers

For some unknown reason this gem now throws this error: `The given SOAPAction checkVat does not match an operation.`

The reason for this is that savon inserts a SOAPaction header that brokes it. This workaround removes that header and the error is no longer risen. I didn't find any other workaround to remove this error. For more info look here:

Savon::SOAPRequest#configure_headers
@Quaresma1997
Copy link

Failed specs. Can you please run them again?

@lubosch
Copy link
Contributor Author

lubosch commented Oct 29, 2021

I have no idea what truffleruby is and I didn't touch normalize function so probably sth else should be fixed also

@Quaresma1997
Copy link

Ok, for now I'll fork your PR and use it on my project.

@yolk
Copy link
Owner

yolk commented Oct 29, 2021

Thanks @lubosch for the fix. I can confirm the error. Seems to be a change in the WDSL-file, which savon isn't handling correctly.

The error in truffleruby seems to be completly unrelated.

klouvas added a commit to Workable/valvat that referenced this pull request Oct 29, 2021
@yolk yolk merged commit 8d1397b into yolk:master Oct 29, 2021
@Quaresma1997
Copy link

Will you send a new release?

@yolk
Copy link
Owner

yolk commented Oct 29, 2021

Yes. Give me some minutes.

@yolk
Copy link
Owner

yolk commented Oct 29, 2021

Just released v1.1.2 including the fix.

@hagi
Copy link

hagi commented Nov 2, 2021

@yolk any chance for 1.0.2 version with this fix for legacy systems?

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

Successfully merging this pull request may close these issues.

None yet

4 participants