Monday, October 12, 2020

Investigation and fix for SubmitCurrentVisitorOrder: Object reference not set to an instance of an object.

Recently, We got this issue while processing the order, Here are the investigation and fix details

We did a third party payment integration and while the payment party submit the success request to our website (XP + XC 9.3) we took the transaction details, Add a new components and send it to create the order.

The order created successfully but XC didn't redirect to order confirmation page, I think the process is after the order submission XC internally call the SubmitCurrentVisitorOrder to get the order details and show to the order confirmation page.



Investigation -  The error was clear the context was missing of visitor could be related to ant forgery or some missing handshake.

the point was the it was working fine in Firefox browser, so first we compare all cookies and session with Mozila and found a diff.


Mozila - We didn't find any diff.



We noticed that in Chrome there are mismatch in the ASP.NET_SessionId and there are a few missing cookies Global Analytics.

We have disabled the analytics and after that we found the same ASP.NET_SessionId and Analytics cookies,

So the issue was related to analytics, We have turned it off and raised a Sitecore ticket for the further investigation, I will keep you posted for the further update.



No comments:

Post a Comment