-
Notifications
You must be signed in to change notification settings - Fork 23
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
Conflict between prod and sandbox api #229
Comments
Hello again, We've downloaded the source code of the SDK, did some searching and found the issue. The cause of the problem is usage of singleton RestSharpDto instead of map-per-url. I can push the code or you can make the changes yourselves, it's not a biggie: Cheers, PS - as a side issue, the HTTP response code returned with the erroneous behaviour was 0 and the message null which caused a NPE in the SDK: |
PR with the changes: #230 |
Hello @iulian03, I've just noticed there's a new 3.19.3 version of the SDK but the error above stops us from migrating to it. Could you include the fix we provided? |
Hi @lukaszbajorski-filmbooking , |
Thanks @iulian03! |
Hello @iulian03, Any luck with planning this in? |
Hello folks,
In our use case we need to be able to switch between prod and sandbox mangopay endpoints dynamically, depending on the data in the running system. Unfortunately, it seems there's an underlying conflict making it impossible. Perhaps a state that the SDK keeps that prevents changing Client+ClientPassword+BaseUrl combo on the fly?
Any help or direction will be appreciated.
Cheers,
Łukasz
The text was updated successfully, but these errors were encountered: