Hey @coding_martian, we've seen this bug before and at one point had a fix for it, there may have been a regression.
However, I believe users of your search experience will typically never see this error. AFAIK this can only occur to someone who has logged into the App Search dashboard, which is likely why you are experiencing it.
You can probably work around this for now by clearing cookies for the app search domain or terminating your current browser session and starting a new one.
Regardless, we will be working on a fix for this on our end.