It may be relevant. The way the shipping calculation works is by storing the session in the order and restoring this on the callback from Vipps (where there are no cookies; but anyway these would have referred to the same session.).
If this session is somehow invalidated between the order being created and the arrival of the shipping callback, the old session will be gone and with it the cart used to calculate shipping. The “no shipping required” option will then occur because the alternative would be to throw an error. Creating accounts/logging in may invalidate a session.
I’ve seen this happen very occasionally but not been able to replicate it. There is no step in the express checkout flow where the user is asked to create an account after the express checkout has started, but before the shipping callback arrives. Do you have an inkling as to how this is done in your case?
I think it should be possible to create a failsafe for this situation but I have not been able to replicate it on demand, so testing will be a problem.
Thread Starter
Kim
(@kimikaze)
I have been able to reproduce this issue.
1 tab open on a product, created an account in another tab, then pressed the “Buy now with Vipps” button on the product in the first tab.
Ok, thank you; that means this process will invalidate the session containing the shipping alternatives. I’ll look into a fix for this.
