Closed hanleyhansen closed 7 years ago
This is not expected behavior.
it seems it is being popped in weird order. in environment code, will you insert logging code in enter and exit to catch what's happened?
I'm seeing this as well. In my scenario the validation is done inside a multithreaded wsgi server. So this library does not appear to be thread safe.
To be honest, I don't really get why one want to use a global stack. I'd prefer to pass the environment as a variable to verify() or have verify() be a member variable of the environment.
despite that, it's a really useful library – thanks.
When is the future? :) I'm getting these errors as well, running itunes-iap 2.3.0. Thanks for the otherwise very useful library.
Hello jox, beschulz's fix is great but I need to test it is breaking backward compatibility or not. (Or developing a new backward-compatibility mode)
Yes - it is mostly because I wasn't taking care of this project for a while. But you reminded it. thanks. Let's see I will take a chance to look at this.
@youknowone thanks for responding!
I patched my installation and it is not backwards compatible, that I can say. But it fixes the problem.
It would be great if you could take a look.
I found mmeisinger made a patch of it already. You can check the new api at the README.
itunesiap.verify(receipt, env=itunesiap.env.review)
@youknowone Thank you!
I'm getting the following error when trying to validate in sandbox mode:
Any ideas?
Here is my code: