Hi Brian and Lily,
We fixed this bug in v1.6 of the SDK, which you can read about in this post. To incorporate this fix into your Answers experience, the client will need to update the version in their search bar integration (instructions here). Upgrading to the latest version possible will allow you to take advantage of the latest features.
You can find what version the search bar is currently using by inspecting the HTML of the page the search bar exists on and searching for “answers” to locate the search bar, like so:
