>Find out the reason!
>
> If you're sure the code base is the same then it must be that either that
>(a) you are using different data
>(b) (just possible) code is expecting the item to be populated before an async call completes and your connection is slower.
>
>Either way, put a breakpoint on the original code and look at the stack trace that led to that situation.....
>
>It's possible that your fix is a valid one - but you don't know that.
>

b) could be a reason although we're testing everything locally. I've been tracing that code and my second attachment in the message shows the stack.

In any case, I already fixed these errors as I spent too much time yesterday on that issue while I was supposed to work on a completely different project.