I have the same issue though only locally.
Not really sure why though, haven’t had time to look into it more closely but I suspect it’s some cookie/session issues.
I have noticed bing bot causing this on my project. I have added nullchecks that returns empty views and the errors have stopped.
More specifically, the bingbots somehow follow the clicks on filter… but they dont understand thta they need to include litium-context (current channel, current page etc) so the requestlookupinfo is null and exception is logged.